8000 [WCM] Add information on code property population by aeoris · Pull Request #2302 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

[WCM] Add information on code property population #2302

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

Closed
wants to merge 3 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fixing typo and formatting
  • Loading branch information
aeoris committed Mar 13, 2013
commit 6c0598586ff60da32e012350c810ae64591c8868
5 changes: 3 additions & 2 deletions book/validation.rst
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
keen.. index::
.. index::
single: Validation

Validation
Expand Down Expand Up @@ -462,7 +462,8 @@ options can be specified in this way.
This is purely meant to make the configuration of the most common option of
a constraint shorter and quicker.

Every constraint has an extra option, `code`, which allows you to specify an error code on a per-use basis.
Every constraint has an extra option, `code`, which allows you to specify an error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should use double backtricks, instead of a single one. Single ones indicate an anchor in Rst.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

code on a per-use basis.

If you're ever unsure of how to specify an option, either check the API documentation
for the constraint or play it safe by always passing in an array of options
Expand Down
0