Locale
Warning: You are browsing the documentation for Symfony 4.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
Validates that a value is a valid locale.
The "value" for each locale is any of the ICU format locale IDs. For example,
the two letter ISO 639-1 language code (e.g. fr
), or the language code
followed by an underscore (_
) and the ISO 3166-1 alpha-2 country code
(e.g. fr_FR
for French/France).
Applies to | property or method |
Class | Locale |
Validator | LocaleValidator |
Basic Usage
1 2 3 4 5 6 7 8 9 10 11 12 13 14
// src/Entity/User.php
namespace App\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class User
{
/**
* @Assert\Locale(
* canonicalize = true
* )
*/
protected $locale;
}
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
canonicalize
type: boolean
default: false
4.1
Using this option with value false
was deprecated in Symfony 4.1 and it
will throw an exception in Symfony 5.0. Use true
instead.
If true
, the Locale::canonicalize() method will be applied before checking
the validity of the given locale (e.g. FR-fr.utf8
is transformed into fr_FR
).
groups
type: array
| string
It defines the validation group or groups of this constraint. Read more about validation groups.
message
type: string
default: This value is not a valid locale.
This message is shown if the string is not a valid locale.
You can use the following parameters in this message:
Parameter | Description |
---|---|
{{ value }} |
The current (invalid) value |
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.