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.
45 lines
1.2 KiB
PHP
45 lines
1.2 KiB
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;
|
|
|
|
/**
|
|
* A container for validation metadata of a property.
|
|
*
|
|
* What exactly you define as "property" is up to you. The validator expects
|
|
* implementations of {@link MetadataInterface} that contain constraints and
|
|
* optionally a list of named properties that also have constraints (and may
|
|
* have further sub properties). Such properties are mapped by implementations
|
|
* of this interface.
|
|
*
|
|
* @author Bernhard Schussek <bschussek@gmail.com>
|
|
*
|
|
* @see MetadataInterface
|
|
*/
|
|
interface PropertyMetadataInterface extends MetadataInterface
|
|
{
|
|
/**
|
|
* Returns the name of the property.
|
|
*
|
|
* @return string The property name.
|
|
*/
|
|
public function getPropertyName();
|
|
|
|
/**
|
|
* Extracts the value of the property from the given container.
|
|
*
|
|
* @param mixed $containingValue The container to extract the property value from.
|
|
*
|
|
* @return mixed The value of the property.
|
|
*/
|
|
public function getPropertyValue($containingValue);
|
|
}
|