Given that Symfony's validator is based on Java's validator, I was checking the Bean Validation 2.0 standard to see if they introduced new features that we could implement too.

These are the new constraints that Symfony doesn't define yet (although you can implement them indirectly with other existing constraints):

Dates:

• @Past
• @PastOrPresent
• @Future
• @FutureOrPresent

Numbers:

• @Positive
• @PositiveOrZero
• @Negative
• @NegativeOrZero

In addition, Hibernate Validator, the only official implementation of Bean Validator 2.0, defines other constraints:

• @CreditCardNumber (it does just the Luhn algorithm check, via the @LuhnCheckValidator but I guess they defined this alias to make it easier to find and understand).
• @EAN for barcode numbers.
• @SafeHtml validates that the string does not contain malicious code. It uses an external sanitizer library.

Are we interested in implementing any of these constraints?