Skip to content

Commit ac72c04

Browse files
committed
Tweak
1 parent a2d1dd8 commit ac72c04

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

forms.rst

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -460,14 +460,11 @@ Before using validation, add support for it in your application:
460460
$ composer require symfony/validator
461461
462462
Validation is done by adding a set of rules, called (validation) constraints,
463-
to a class.
463+
to a class. You can add them either to the entity class or to the form class.
464464

465-
There are two approaches - you can either add the constraints to the entity,
466-
or you can add the constraints to the form.
467-
468-
To see the first approach - adding constraints to the entity - in action,
465+
To see the first approach - adding constraints to the entity - in action,
469466
add the validation constraints, so that the ``task`` field cannot be empty,
470-
and the ``dueDate`` field cannot be empty, and must be a valid \DateTime
467+
and the ``dueDate`` field cannot be empty, and must be a valid ``DateTime``
471468
object.
472469

473470
.. configuration-block::
@@ -550,9 +547,9 @@ object.
550547
}
551548
552549
That's it! If you re-submit the form with invalid data, you'll see the
553-
corresponding errors printed out with the form.
550+
corresponding errors printed out with the form.
554551

555-
To see the second approach - adding constraints to the form and to
552+
To see the second approach - adding constraints to the form - and to
556553
learn more about the validation constraints, please refer to the
557554
:doc:`Symfony validation documentation </validation>`.
558555

0 commit comments

Comments
 (0)