@felds Your initial issue could be used by using validation groups (i.e. validate the numeric type before validating the value). So the only problem this is solving is saving some chars.

To be complete you should also update theValidatorTypeGuesser (see howMin andMax are used there).

@vicb do you mean running the validators twice?

I mean using group sequences.

@vicb I didn't know about that (and google isn't helping). How can I learn more about that?

There should be a couple of PR / issues that you can look for in Sf or Sf-doc (#2947 for example). I am not sure if this is already documented... Can you check ? (and if it is not, please create an issue or even better a PR)

And also by looking at the tests

@felds Besides such a constraint already exists (at least in master, not sure about 2.0): theSize constraint.
The name may not be appropriate but it does the exact same thing.

@jalliot you are right, thanks.@felds can you still check the doc ?

@vicb AFAIK @bschussek (or anyone else) never had time to write something in the doc about group sequences and he seems to be the only one who know them well enough.

I created an issue in the doc:symfony/symfony-docs#1248

thanks