This project is read-only.


ModelPropertyValidator - one validator per model property instead of validator per model



haypet wrote:
In regards to VAB, in reality it uses same method as a regular validation, so one server tag per control (EntLibValidators:PropertyProxyValidator). It might seem not logical at the beginning, but again, you need to accomodate UI design issues too, and for that it is easier to have separate control, otherwise you will have limited abilities in placing error message.

You are absolutely correct. Separate validators for each property does make more sense from a UI perspective. Thanks for pointing out something that should have been obvious to me! Perhaps I'll add a ModelPropertyValidator in the next release.
Closed Feb 3, 2012 at 5:59 PM by jrummell


haypet wrote Aug 30, 2010 at 1:36 AM

Hi there,

I recently downloaded latest version (0.3) and didn't find new property which allows one validator per coltro. Had this been implemented?


jrummell wrote Aug 30, 2010 at 4:01 AM

Not yet.

jrummell wrote Jun 16, 2011 at 2:28 AM

Fixed in jQuery.Validate branch