beanvalidation/beanvalidation.org — comment on commit bc37cfec514b79f7695ccb35f9990115c5fdeab8
File: proposals/BVAL-241.md line 553
By emmanuelbernard:

My concern is the explosion of methods on `Validator` that become unreadable. That's why I proposed this approach to limit its pollution.

The cons I can see is that if at some points constructors have setting that methods don't have or vice versa, we will need to revise this approach many by subclassing of `MethodValidator`.

Personally, I think this approach is worth it. Also note that the design is consistent with `getConstraintsForClass`. My idea was to let major methods on `Validator` and put minor ones behind an indirection.