I second that. Data annotation validations work well for a CRUD type of feature, less so for relational constraints.
I'm working on this domain where computers are leased to customers. In order to record a dispatch, many fields have to be filled in. But there's rules about field values that limit the valid options for other fields. I implemented just the basic ones.
The real challenge would be formalize the rules in such a way you can get the most efficient decision tree in the UI as well being able to validate command input :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I second that. Data annotation validations work well for a CRUD type of feature, less so for relational constraints.
I'm working on this domain where computers are leased to customers. In order to record a dispatch, many fields have to be filled in. But there's rules about field values that limit the valid options for other fields. I implemented just the basic ones.
The real challenge would be formalize the rules in such a way you can get the most efficient decision tree in the UI as well being able to validate command input :)