-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feature #4724 [Reference][Constraints] document the validation payloa…
…d option (xabbuh) This PR was merged into the 2.6 branch. Discussion ---------- [Reference][Constraints] document the validation payload option | Q | A | ------------- | --- | Doc fix? | no | New docs? | yes (symfony/symfony#12005) | Applies to | 2.6+ | Fixed tickets | #4274 Commits ------- dca4655 document the validation payload option
- Loading branch information
Showing
48 changed files
with
315 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,3 +5,4 @@ Validation | |
:maxdepth: 2 | ||
|
||
custom_constraint | ||
severity |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,165 @@ | ||
.. index:: | ||
single: Validation; Error Levels | ||
single: Validation; Payload | ||
|
||
How to Handle Different Error Levels | ||
==================================== | ||
|
||
Sometimes, you may want to display constraint validation error messages differently | ||
based on some rules. For example, you have a registration form for new users | ||
where they enter some personal information and choose their authentication | ||
credentials. They would have to choose a username and a secure password, | ||
but providing bank account information would be optional. Nonetheless, you | ||
want to make sure that these optional data, if entered, are still valid, | ||
but display them differently. | ||
|
||
The process to achieve this behavior consists of two steps: | ||
|
||
#. Apply different error levels to the validation constraints; | ||
#. Customize your error messages depending on the configured error level. | ||
|
||
1. Assigning the Error Level | ||
---------------------------- | ||
|
||
.. versionadded:: 2.6 | ||
The ``payload`` option was introduced in Symfony 2.6. | ||
|
||
Use the ``payload`` option to configure the error level for each constraint: | ||
|
||
.. configuration-block:: | ||
|
||
.. code-block:: php-annotations | ||
// src/AppBundle/Entity/User.php | ||
namespace AppBundle\Entity; | ||
use Symfony\Component\Validator\Constraints as Assert; | ||
class User | ||
{ | ||
/** | ||
* @Assert\NotBlank(payload = {severity = "error"}) | ||
*/ | ||
protected $username; | ||
/** | ||
* @Assert\NotBlank(payload = {severity = "error"}) | ||
*/ | ||
protected $password; | ||
/** | ||
* @Assert\Iban(payload = {severity = "warning"}) | ||
*/ | ||
protected $bankAccountNumber; | ||
} | ||
.. code-block:: yaml | ||
# src/AppBundle/Resources/config/validation.yml | ||
AppBundle\Entity\User: | ||
properties: | ||
username: | ||
- NotBlank: | ||
payload: | ||
severity: error | ||
password: | ||
- NotBlank: | ||
payload: | ||
severity: error | ||
bankAccountNumber: | ||
- Iban: | ||
payload: | ||
severity: warning | ||
.. code-block:: xml | ||
<!-- src/AppBundle/Resources/config/validation.xml --> | ||
<?xml version="1.0" encoding="UTF-8" ?> | ||
<constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping" | ||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping http://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd"> | ||
<class name="AppBundle\Entity\User"> | ||
<property name="username"> | ||
<constraint name="NotBlank"> | ||
<option name="payload"> | ||
<value key="severity">error</value> | ||
</option> | ||
</constraint> | ||
</property> | ||
<property name="password"> | ||
<constraint name="NotBlank"> | ||
<option name="payload"> | ||
<value key="severity">error</value> | ||
</option> | ||
</constraint> | ||
</property> | ||
<property name="bankAccountNumber"> | ||
<constraint name="Iban"> | ||
<option name="payload"> | ||
<value key="severity">warning</value> | ||
</option> | ||
</constraint> | ||
</property> | ||
</class> | ||
</constraint-mapping> | ||
.. code-block:: php | ||
// src/AppBundle/Entity/User.php | ||
namespace AppBundle\Entity; | ||
use Symfony\Component\Validator\Mapping\ClassMetadata; | ||
use Symfony\Component\Validator\Constraints as Assert; | ||
class User | ||
{ | ||
public static function loadValidatorMetadata(ClassMetadata $metadata) | ||
{ | ||
$metadata->addPropertyConstraint('username', new Assert\NotBlank(array( | ||
'payload' => array('severity' => 'error'), | ||
))); | ||
$metadata->addPropertyConstraint('password', new Assert\NotBlank(array( | ||
'payload' => array('severity' => 'error'), | ||
))); | ||
$metadata->addPropertyConstraint('bankAccountNumber', new Assert\Iban(array( | ||
'payload' => array('severity' => 'warning'), | ||
))); | ||
} | ||
} | ||
2. Customize the Error Message Template | ||
--------------------------------------- | ||
|
||
.. versionadded:: 2.6 | ||
The ``getConstraint()`` method in the ``ConstraintViolation`` class was | ||
introduced in Symfony 2.6. | ||
|
||
When validating the ``User`` object failed, you can retrieve the constraint | ||
that caused a particular failure using the | ||
:method:`Symfony\\Component\\Validator\\ConstraintViolation::getConstraint` | ||
method. Each constraint exposes the attached payload as a public property:: | ||
|
||
// a constraint validation failure, instance of | ||
// Symfony\Component\Validator\ConstraintViolation | ||
$constraintViolation = ...; | ||
$constraint = $constraintViolation->getConstraint(); | ||
$severity = isset($constraint->payload['severity']) ? $constraint->payload['severity'] : null; | ||
|
||
For example, you can leverage this to customize the ``form_errors`` block | ||
such that the severity is added as an additional HTML class: | ||
|
||
.. code-block:: html+jinja | ||
|
||
{%- block form_errors -%} | ||
{%- if errors|length > 0 -%} | ||
<ul> | ||
{%- for error in errors -%} | ||
{% if error.cause.constraint.payload.severity is defined %} | ||
{% set severity = error.cause.constraint.payload.severity %} | ||
{% endif %} | ||
<li{% if severity is defined %} class="{{ severity }}"{% endif %}>{{ error.message }}</li> | ||
{%- endfor -%} | ||
</ul> | ||
{%- endif -%} | ||
{%- endblock form_errors -%} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.