Skip to content
[READ-ONLY] Subtree split of the Symfony Validator Component -- clone into Symfony/Component/ (master at symfony/symfony)
Latest commit 269f6bd @fabpot fabpot updated version to 3.1
Failed to load latest commit information.
Constraints Merge branch '2.8'
Context [3.0] Remove more deprecated interfaces in Form and Validator
Exception fixes CS
Mapping [3.0] Clean Form, Validator, DowCrawler and some more
Resources/translations minor #16610 Add Spanish translation for BIC validator (ajgarlag)
Tests Merge branch '2.8'
Util [Validator] Property paths starting with 0 are broken.
Validator [3.0] Various deprecations cleanups
Violation [Validator] removed deprecated methods
.gitignore Added missing files .gitignore [Validator] added BIC (SWIFT-BIC) validation constraint
Constraint.php Merge branch '2.3' into 2.7
ConstraintValidator.php [Validator] removed deprecated methods
ConstraintValidatorFactory.php Merge branch '2.4'
ConstraintValidatorFactoryInterface.php removed unneeded use statements
ConstraintValidatorInterface.php [Validator] removed deprecated methods
ConstraintViolation.php [Validator] removed deprecated methods
ConstraintViolationInterface.php [Validator] removed deprecated methods
ConstraintViolationList.php made {@inheritdoc} annotations consistent across the board
ConstraintViolationListInterface.php remove api tags from code
GroupSequenceProviderInterface.php fixed CS
LICENSE Updated copyright to 2015
ObjectInitializerInterface.php remove api tags from code updated version to 3.1
Validation.php [Validator] remove the API_VERSION
ValidatorBuilder.php [3.0] Remove more deprecated interfaces in Form and Validator
ValidatorBuilderInterface.php [3.0] Remove more deprecated interfaces in Form and Validator
composer.json updated version to 3.1
phpunit.xml.dist Add missing exclusions from phpunit.xml.dist

Validator Component

This component is based on the JSR-303 Bean Validation specification and enables specifying validation rules for classes using XML, YAML, PHP or annotations, which can then be checked against instances of these classes.


The component provides "validation constraints", which are simple objects containing the rules for the validation. Let's validate a simple string as an example:

use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints\Length;

$validator = Validation::createValidator();

$violations = $validator->validateValue('Bernhard', new Length(array('min' => 10)));

This validation will fail because the given string is shorter than ten characters. The precise errors, here called "constraint violations", are returned by the validator. You can analyze these or return them to the user. If the violation list is empty, validation succeeded.

Validation of arrays is possible using the Collection constraint:

use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;

$validator = Validation::createValidator();

$constraint = new Assert\Collection(array(
    'name' => new Assert\Collection(array(
        'first_name' => new Assert\Length(array('min' => 101)),
        'last_name' => new Assert\Length(array('min' => 1)),
    'email' => new Assert\Email(),
    'simple' => new Assert\Length(array('min' => 102)),
    'gender' => new Assert\Choice(array(3, 4)),
    'file' => new Assert\File(),
    'password' => new Assert\Length(array('min' => 60)),

$violations = $validator->validateValue($input, $constraint);

Again, the validator returns the list of violations.

Validation of objects is possible using "constraint mapping". With such a mapping you can put constraints onto properties and objects of classes. Whenever an object of this class is validated, its properties and method results are matched against the constraints.

use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;

class User
     * @Assert\Length(min = 3)
     * @Assert\NotBlank
    private $name;

     * @Assert\Email
     * @Assert\NotBlank
    private $email;

    public function __construct($name, $email)
        $this->name = $name;
        $this->email = $email;

     * @Assert\IsTrue(message = "The user should have a Google Mail account")
    public function isGmailUser()
        return false !== strpos($this->email, '');

$validator = Validation::createValidatorBuilder()

$user = new User('John Doe', '');

$violations = $validator->validate($user);

This example uses the annotation support of Doctrine Common to map constraints to properties and methods. You can also map constraints using XML, YAML or plain PHP, if you dislike annotations or don't want to include Doctrine. Check the documentation for more information about these drivers.


Silex integration:


JSR-303 Specification:

You can run the unit tests with the following command:

$ cd path/to/Symfony/Component/Validator/
$ composer install
$ phpunit
Something went wrong with that request. Please try again.