-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Validator] Added documentation for Traverse constraint #11310
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
Conversation
e7391ba
to
86ee59e
Compare
Woohoo, yet another undocumented feature documented! #EUFOSSA |
…t (HeahDude) This PR was squashed before being merged into the 3.4 branch (closes #11310). Discussion ---------- [Validator] Added documentation for Traverse constraint ```rst versionadded:: 2.5 The traverse constraint has been added in Symfony 2.5 ``` x) Commits ------- 86ee59e [Validator] Added documentation for Traverse constraint
+----------------+-------------------------------------------------------------------------------------+ | ||
| Options | - `payload`_ | | ||
+----------------+-------------------------------------------------------------------------------------+ | ||
| Class | :class:`Symfony\\Bridge\\Doctrine\\Validator\\Constraints\\Traverse` | |
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.
Is the namespace valid? I find it here: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Validator/Constraints/Traverse.php 🤔
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.
Also, why isn't there any dedicated validator for this specific constraint?
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.
See #11320. Like Valid
those constraints are handled by the recursive context itself to define the cascade strategy, so do not need custom validator.
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.
Ooh, TIL, thanks 😄
Sorry to be late (and thanks for improving the docs) but it seems that it doesn't work that way... the example throws;
|
x)