Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[Validator] Fix@Valid regarding propertytraverse#10868
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
fa004a4 to49354b4Compare49354b4 to8ed269fCompare8ed269f to0836a48Compare| 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``. Thisoption 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 ifsymfony/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 to6343b24Compare
HeahDude left a comment
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!
javiereguiluz commentedMar 7, 2019
Thank you@corphi. |
…corphi)This PR was merged into the 3.4 branch.Discussion----------[Validator] Fix `@Valid` regarding property `traverse`While researching forsymfony/symfony#27090, the constraint reference turned out to be incorrect.Commits-------6343b24 Describe actual traversal behaviour
While researching forsymfony/symfony#27090, the constraint reference turned out to be incorrect.