The historical reason for the restricted list of constraints in the BV
spec is that this set represents the fundamental constraints you can
express and often propagate to other systems (like DB DDLs). So the
reluctance came from this and a hope that an ecosystem of constraints
would be built.
But these numbers are interesting (*) and embracing more constraints
looks like a good idea. It is probably worth doing a blog to gather
feedback. Or maybe a survey.
(*) GitHub hosts a list of "non-usual" projects, most 9-5 projects are
behind closed source doors. So there is a natural skew.
Emmanuel
On Mon 2016-08-22 19:37, Marco Molteni wrote:
Hi all,
It would be possible to add some built-in constraints to the V 2.0?
@NotBlank, @NotEmpty, @Length are used very often in projects, they are
already present in Hibernate Validator and their implementation is well
defined.
What do you think?
Here a list of the most used constraint for GitHub's projects (the numbers
change at every request but you get the idea. HV = Hibernate Validator, BV
= Bean Validation):
189'143 - BV - NotNull
56'902 - BV - Size
39'551 - HV - NotEmpty <-
20'687 - HV - NotBlank <-
17'735 - BV - Pattern
16'763 - HV - Email
16'033 - BV - Min
12'769 - HV - Length <-
7'806 - BV - Digits
4'982 - BV - Max
4'971 - BV - Past
3'598 - BV - DecimalMin
2'753 - BV - AssertTrue
2'379 - BV - DecimalMax
2'308 - BV - Future
1'999 - HV - Range
1'497 - HV - URL
< 1'000 other constraints
Thanks
Cheers
Marco
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev