New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Validator] Fix @Valid
regarding property traverse
#10868
Conversation
fa004a4
to
49354b4
Compare
49354b4
to
8ed269f
Compare
8ed269f
to
0836a48
Compare
set to ``true``. | ||
If this constraint is applied to a ``Traversable``, then all containing values | ||
will be validated if this option is set to ``true``. This option is ignored on | ||
arrays: Arrays are traversed in either case. Keys are not validated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should need a correction if symfony/symfony#29800 is merged, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, @Valid
is working correctly. The docs could just use this clarification. The mentioned pull request is only concerned with other constraints not working correctly.
0836a48
to
6343b24
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thank you @corphi. |
…corphi) This PR was merged into the 3.4 branch. Discussion ---------- [Validator] Fix `@Valid` regarding property `traverse` While researching for symfony/symfony#27090, the constraint reference turned out to be incorrect. Commits ------- 6343b24 Describe actual traversal behaviour
While researching for symfony/symfony#27090, the constraint reference turned out to be incorrect.