Skip to content

Commit 7562f64

Browse files
committed
[Validator] Fix list in Sequentially doc
1 parent b511eb5 commit 7562f64

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

reference/constraints/Sequentially.rst

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,17 +25,19 @@ Basic Usage
2525

2626
Suppose that you have a ``Place`` object with an ``$address`` property which
2727
must match the following requirements:
28-
- it's a non-blank string
29-
- of at least 10 chars long
30-
- with a specific format
31-
- and geolocalizable using an external service
28+
29+
* it's a non-blank string
30+
* of at least 10 chars long
31+
* with a specific format
32+
* and geolocalizable using an external service
3233

3334
In such situations, you may encounter three issues:
34-
- the ``Length`` or ``Regex`` constraints may fail hard with a :class:`Symfony\\Component\\Validator\\Exception\\UnexpectedValueException`
35-
exception if the actual value is not a string, as enforced by ``Type``.
36-
- you may end with multiple error messages for the same property
37-
- you may perform a useless and heavy external call to geolocalize the address,
38-
while the format isn't valid.
35+
36+
* the ``Length`` or ``Regex`` constraints may fail hard with a :class:`Symfony\\Component\\Validator\\Exception\\UnexpectedValueException`
37+
exception if the actual value is not a string, as enforced by ``Type``.
38+
* you may end with multiple error messages for the same property
39+
* you may perform a useless and heavy external call to geolocalize the address,
40+
while the format isn't valid.
3941

4042
You can validate each of these constraints sequentially to solve these issues:
4143

0 commit comments

Comments
 (0)