Currency
Edit this pageWarning: You are browsing the documentation for Symfony 4.0, which is no longer maintained.
Read the updated version of this page for Symfony 7.0 (the current stable version).
Currency
Validates that a value is a valid 3-letter ISO 4217 currency name.
Applies to | property or method |
Options | |
Class | Currency |
Validator | CurrencyValidator |
Basic Usage
If you want to ensure that the currency
property of an Order
is
a valid currency, you could do the following:
1 2 3 4 5 6 7 8 9 10 11 12
// src/Entity/Order.php
namespace App\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class Order
{
/**
* @Assert\Currency
*/
protected $currency;
}
1 2 3 4 5
# config/validator/validation.yaml
App\Entity\Order:
properties:
currency:
- Currency: ~
1 2 3 4 5 6 7 8 9 10 11 12
<!-- config/validator/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="App\Entity\Order">
<property name="currency">
<constraint name="Currency" />
</property>
</class>
</constraint-mapping>
1 2 3 4 5 6 7 8 9 10 11 12 13
// src/Entity/Order.php
namespace App\Entity;
use Symfony\Component\Validator\Mapping\ClassMetadata;
use Symfony\Component\Validator\Constraints as Assert;
class Order
{
public static function loadValidatorMetadata(ClassMetadata $metadata)
{
$metadata->addPropertyConstraint('currency', new Assert\Currency());
}
}
Options
message
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.
payload
type: mixed
default: null
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 you.
For example, you may want to use several error levels to present failed constraints differently in the front-end depending on the severity of the error.