Andreas

I added another "test case" to make the confusing behavior a bit more obvious: [Symfony Issue 32900 with Validator.zip](https://github.com/symfony/symfony/files/3464814/Symfony.Issue.32900.with.Validator.zip) It shows in more detail how the validation group definition for...

I went through all the relevant source code in the validator component and found the reasons for the current behavior, and a way to make `Valid` behave the same in...

The main problem I see is that the current behavior is not very useful (and it is not documented) - it does not make sense to me in any project...

Creating a new annotation would be BC compatible, and it would make it possible to give people an "upgrade strategy" and to deprecate the old `Valid` at some point, because...

In a nutshell, this is the behavior I am proposing (I named the annotation `Cascade` here just so it is clear that it is something new), which is what I...

@vudaltsov The problem with the current behavior is that it is not completely fixable - for example `Valid` without a validation group currently always triggers (no matter what validation groups...

I created an open source package to partly solve the problem, with a new `Cascade` annotation: https://github.com/squirrelphp/validator-cascade (MIT licensed) For my projects this is useable, and I included documentation on...

Thanks for your effort! I didn't see an issue for this yet, and v2.5 just came out, so I thought I would mention it in case this wasn't known yet...

It could make sense to use two interfaces - a "user-facing" one that implements the methods to check for holidays, dates, etc. (representing a very stable set of methods that...

It depends on what methods you want to offer and which ones are internal-adjacent - would also make it easier to change the internal-adjacent ones and communicate to users what...