ExpressionSyntax ¶
This constraint checks that the value is valid as an ExpressionLanguage expression.
6.1
This constraint was introduced in Symfony 6.1 and deprecates the previous ExpressionLanguageSyntax constraint.
Applies to | property or method |
Class | ExpressionSyntax |
Validator | ExpressionSyntaxValidator |
Basic Usage ¶
The following constraints ensure that:
- the
promotion
property stores a value which is valid as an ExpressionLanguage expression;プロモーション プロパティは、ExpressionLanguage 式として有効な値を格納します。 - the
shippingOptions
property also ensures that the expression only uses certain variables.shippingOptions プロパティは、式が特定の変数のみを使用することも保証します。
-
Attributes
属性
-
YAML
YAML
-
XML
XML
-
PHP
PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
// src/Entity/Order.php
namespace App\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class Order
{
#[Assert\ExpressionSyntax]
protected $promotion;
#[Assert\ExpressionSyntax(
allowedVariables: ['user', 'shipping_centers'],
)]
protected $shippingOptions;
}
|
Options ¶
allowedVariables ¶
type: array
or null
default: null
If this option is defined, the expression can only use the variables whose names
are included in this option. Unset this option or set its value to null
to
allow any variables.
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 should be a valid expression.
This is the message displayed when the validation fails.
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.