efe42cbb1f
With this refactoring comes a decoupling of the validator from the structure of the underlying metadata. This way it is possible for Drupal to use the validator for validating their Entity API by using their own metadata layer, which is not modeled as classes and properties/getter methods.
38 lines
899 B
PHP
38 lines
899 B
PHP
<?php
|
|
|
|
/*
|
|
* This file is part of the Symfony package.
|
|
*
|
|
* (c) Fabien Potencier <fabien@symfony.com>
|
|
*
|
|
* For the full copyright and license information, please view the LICENSE
|
|
* file that was distributed with this source code.
|
|
*/
|
|
|
|
namespace Symfony\Component\Validator;
|
|
|
|
/**
|
|
* @author Bernhard Schussek <bschussek@gmail.com>
|
|
*
|
|
* @api
|
|
*/
|
|
interface ConstraintValidatorInterface
|
|
{
|
|
/**
|
|
* Initializes the constraint validator.
|
|
*
|
|
* @param ExecutionContextInterface $context The current validation context
|
|
*/
|
|
public function initialize(ExecutionContextInterface $context);
|
|
|
|
/**
|
|
* Checks if the passed value is valid.
|
|
*
|
|
* @param mixed $value The value that should be validated
|
|
* @param Constraint $constraint The constraint for the validation
|
|
*
|
|
* @api
|
|
*/
|
|
public function validate($value, Constraint $constraint);
|
|
}
|