CTL-43: Validation annotations at Class level

[GeertvanHorrik]

CTL-43: Validation annotations at Class level

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

How would this translate into a validator? Can you give us more information how you see this? For example, would the ValidateMeeting provide an IValidator implementation?

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

concerning validation at class (entity) level:

http://jeffhandley.com/archive/2010/10/12/EntityLevelValidation.aspx
This describes it pretty good (especially the first paragraph)…

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

I don't want people having to specify both the validation class and the method. Still considering what's the best way to implement this.

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

Naming conventions are my first thought, but I don't want to force other developers to be forced into a specific naming convention.

[GeertvanHorrik]

Comment created by facos:

Would it be possible to support just a ValidationAttribute at entity level?
I'm also not a friend of specifying both the validation class and the method but
since the CustomValidationAttribute is just a derivation of ValidationAttribute
everybody has the choice to take or not....

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

Improved the Validator implementation. Now the ModelBase checks once whether a IValidatorProvider is registered in the ServiceLocator. If so, it will automatically get the IValidator from the IValidatorProvider.

It is still overridable per model.

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

Written custom AttributeValidatorProvider which caches and should be very, very fast and is registered by default.

Now up to writing unit tests.

[GeertvanHorrik]

Comment created by @GeertvanHorrik:

See the documentation:

https://catelproject.atlassian.net/wiki/display/CTL/Validationviaspecialmodelvalidators

[GeertvanHorrik]

Issue was closed with resolution "Fixed"

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.