[Validator] Fix ValidValidator group cascading usage #33834
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
$this->context->getGroup()
returnsstring
ornull
.ContextualValidatorInterface::validate()
3rd argument accepts an array but it must not containnull
(its contract doesn't allow it). If it does, it will fail inRecursiveContextualValidator::validateInGroup()
for example because of thestring
scalar type on the$group
argument. (on 4.4)Note that in our "common" usage of the
Valid
constraint, the group in its validator will never benull
because this constraint has a special treatment. However, if this validator is reused in a custom way, it can fail.