I don't remember the exact circumstance, but the example from my previous comment is probably what motivated be to comment on the issue.

My specific example (increasing maximum length) requires overriding, not disabling. I'd think that it's a matter of updating the property of a validation annotation. Something like a base class having a @Min(value=1) and a subclass requiring @Min(value=2).

Re: Liskov Substitution Principle - please make this validation library as general as possible. Adhering to strict OO principles is great and all, but we don't all get to develop object models from scratch. I've got to deal with data structures over a decade old. I can either do it all with HV, or do some in HV and write yet more validation code elsewhere. I'd much prefer to centralize all validation related to the data in one single place.

Unless there's a huge technical challenge to enabling this, forcing everyone to redesign their data models seems a bit harsh.

Still, I'm glad you're circling back around to this!