Currency

Currency

Validates that a value is a valid 3-letter ISO 4217 currency name.

Basic Usage

If you want to ensure that the currency property of an Order is a valid currency, you could do the following:

• Annotations

  // src/Entity/Order.php
  namespace App\Entity;
  use Symfony\Component\Validator\Constraints as Assert;
  class Order
  {
      /**
       * @Assert\Currency
       */
      protected $currency;
  }

• YAML

  # config/validator/validation.yaml
  App\Entity\Order:
      properties:
          currency:
              - Currency: ~

• XML

  <!-- 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 https://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>

• PHP

  // src/Entity/Order.php
  namespace App\Entity;
  use Symfony\Component\Validator\Constraints as Assert;
  use Symfony\Component\Validator\Mapping\ClassMetadata;
  class Order
  {
      public static function loadValidatorMetadata(ClassMetadata $metadata)
      {
          $metadata->addPropertyConstraint('currency', new Assert\Currency());
      }
  }

Note

As with most of the other constraints, null and empty strings are considered valid values. This is to allow them to be optional values. If the value is mandatory, a common solution is to combine this constraint with NotBlank.

Options

groups

type: array | string

It defines the validation group or groups this constraint belongs to. Read more about validation groups.

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.

You can use the following parameters in this message:

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.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.