Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit571c7d7

Browse files
committed
Merge branch '6.2' into 6.3
* 6.2: [Form] Improve form validation section
2 parentse281629 +7d49f56 commit571c7d7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

‎forms.rst‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -468,7 +468,8 @@ Before using validation, add support for it in your application:
468468
$ composer require symfony/validator
469469
470470
Validation is done by adding a set of rules, called (validation) constraints,
471-
to a class. You can add them either to the entity class or to the form class.
471+
to a class. You can add them either to the entity class or by using the
472+
:ref:`constraints option<reference-form-option-constraints>` of form types.
472473

473474
To see the first approach - adding constraints to the entity - in action,
474475
add the validation constraints, so that the ``task`` field cannot be empty,
@@ -553,9 +554,8 @@ object.
553554
That's it! If you re-submit the form with invalid data, you'll see the
554555
corresponding errors printed out with the form.
555556

556-
To see the second approach - adding constraints to the form - and to
557-
learn more about the validation constraints, please refer to the
558-
:doc:`Symfony validation documentation</validation>`.
557+
To see the second approach - adding constraints to the form - refer to
558+
:ref:`this section<form-option-constraints>`. Both approaches can be used together.
559559

560560
Other Common Form Features
561561
--------------------------

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp