/propage/propagate/ in your commit message :)

can we please close either#23480 or this one? both address the same problem and propose the same fixing strategy.

Using$contraint->groups is wrong. You need to use$context->getGroup(), because that is the group that is actually validated in the current call of the contraints validator.
The following produces a violation with this PR, but it should not:

$contraint =newCollection(['fields' => ['key' =>newLength(['min' =>6, groups => ['b']]),  ],'groups' => ['a','b'],]);$validator->validate(['key' =>'value' ],$contraint,'a');

From my point of view we have a 2 possibilities:

1. Deprecate/disallow validation groups in nested contraints, because they dont work correctly and document the use case presented in[Validator] All validation groups are not used on embedded constraints in a collection constraint #17675 and[Validator] Incorrect collection validation with different groups #23479 to use multipleCollection andAll constraints (something like here[Validator] All validation groups are not used on embedded constraints in a collection constraint #17675 (comment) but with groups moved to the composite contraint)
2. Disable caching for composite contraints (and optionally deprecate/disallow validation groups on composite contraints)
3. Change the caching strategy

I'm not sure there is really an issue here, just a misusage while not being aware ofhttps://github.com/symfony/symfony/blob/master/src/Symfony/Component/Validator/Constraints/Composite.php#L34-L48 (documentation issue).

Actually#17675 (comment), could be written:

/**     * @Collection(     *     fields={     *          "foo" = {     *              @NotBlank(groups={"foo"}),     *              @Length(min="2", groups={"bar"}),     *              @Length(min="4", groups={"baz"}),     *          }     *     },     *    groups={"foo", "bar", "baz"}     * )     */

And this should be the way to go IMHO.

This doesnt work with grp sequences

So this is what needs to be fixed :). Could you please update your tests here@blazarecki?

Yes I'll do that.

@blazarecki imho there is nothing wrong with grp sequences. the possible fix path are described in my comment above. Despite the comment inhttps://github.com/symfony/symfony/blob/master/src/Symfony/Component/Validator/Constraints/Composite.php#L34 different grps for composite contraint and nested constraints just dont work.

If we dont want to change anything, then my proposed solution 1 is a good way.
If we want to support grps on nested contraints correctly, then contraints must be able to opt out of caching (my solution 2). Maybe with a marker interface or a contraint setting (a setting that is decided at dev time of the contraint). This also requires, that a contraint, that does not get cached,never does any validation of its own, but depends for the decision "pass" or "not pass" entirely and only on its nested contraints.

@HeahDude As you started to work on this one (at least commenting on it) I need your help for the next steps (related to#23480 as well)?

Any help needed with this one? Comments seem to be addressed and tests passing.

@artursvonda tell me if I need to change something.

Just wanted to bump up the ticket since comments already seem to be addressed.@fabpot@HeahDude ?

As said in my previous comment, there is no issue to fix as is.

@HeahDude so in my issue#23479 (and related pr#23480) there is no issue too, you think?

Thank you all for your input and working on this. This is finally going to be fixed in#29499.