发布于 2015-08-27 16:36:32 | 100 次阅读 | 评论: 0 | 来源: 网络整理
2.3 新版功能: The Currency constraint was introduced in Symfony 2.3.
Validates that a value is a valid 3-letter ISO 4217 currency name.
| Applies to | property or method |
| Options | |
| Class | Currency |
| Validator | CurrencyValidator |
If you want to ensure that the currency property of an Order is a valid
currency, you could do the following:
# src/Acme/EcommerceBundle/Resources/config/validation.yml
AcmeEcommerceBundleEntityOrder:
properties:
currency:
- Currency: ~
// src/Acme/EcommerceBundle/Entity/Order.php
namespace AcmeEcommerceBundleEntity;
use SymfonyComponentValidatorConstraints as Assert;
class Order
{
/**
* @AssertCurrency
*/
protected $currency;
}
<!-- src/Acme/EcommerceBundle/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="AcmeEcommerceBundleEntityOrder">
<property name="currency">
<constraint name="Currency" />
</property>
</class>
</constraint-mapping>
// src/Acme/EcommerceBundle/Entity/Order.php
namespace AcmeSocialBundleEntity;
use SymfonyComponentValidatorMappingClassMetadata;
use SymfonyComponentValidatorConstraints as Assert;
class Order
{
public static function loadValidatorMetadata(ClassMetadata $metadata)
{
$metadata->addPropertyConstraint('currency', new AssertCurrency());
}
}
type: string default: This value is not a valid currency.
This is the message that will be shown if the value is not a valid currency.
type: mixed default: null
2.6 新版功能: The payload option was introduced in Symfony 2.6.
This option can be used to attach arbitrary domain-specific data to a constraint. The configured payload is not used by the Validator component, but its processing is completely up to.
For example, you may want to used several error levels to present failed constraint differently in the front-end depending on the severity of the error.