Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[Validator] Deprecate constraint "ExpressionLanguageSyntax", use "ExpressionSyntax" instead#16786

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletionreference/constraints.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -14,7 +14,8 @@ Validation Constraints Reference
constraints/Type

constraints/Email
constraints/ExpressionLanguageSyntax
constraints/ExpressionLanguageSyntax (deprecated)
constraints/ExpressionSyntax
constraints/Length
constraints/Url
constraints/Regex
Expand Down
5 changes: 5 additions & 0 deletionsreference/constraints/ExpressionLanguageSyntax.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
ExpressionLanguageSyntax
========================

.. deprecated:: 6.1

This constraint is deprecated since Symfony 6.1.
Use the``ExpressionSyntax`` constraint instead.

This constraint checks that the value is valid as an `ExpressionLanguage`_
expression.

Expand Down
147 changes: 147 additions & 0 deletionsreference/constraints/ExpressionSyntax.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
ExpressionSyntax
================

This constraint checks that the value is valid as an `ExpressionLanguage`_
expression.

.. info:: 6.1

This constraint is deprecated since Symfony 6.1.
Use the``ExpressionSyntax`` constraint instead.

========== ===================================================================
Applies to :ref:`property or method <validation-property-target>`
Class :class:`Symfony\\Component\\Validator\\Constraints\\ExpressionSyntax`
Validator :class:`Symfony\\Component\\Validator\\Constraints\\ExpressionSyntaxValidator`
========== ===================================================================

Basic Usage
-----------

The following constraints ensure that:

* the ``promotion`` property stores a value which is valid as an
ExpressionLanguage expression;
* the ``shippingOptions`` property also ensures that the expression only uses
certain variables.

.. configuration-block::

.. code-block:: php-annotations

// 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;
}

.. code-block:: php-attributes

// 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;
}

.. code-block:: yaml

# config/validator/validation.yaml
App\Entity\Order:
properties:
promotion:
- ExpressionSyntax: ~
shippingOptions:
- ExpressionSyntax:
allowedVariables: ['user', 'shipping_centers']

.. code-block:: 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="promotion">
<constraint name="ExpressionSyntax"/>
</property>
<property name="shippingOptions">
<constraint name="ExpressionSyntax">
<option name="allowedVariables">
<value>user</value>
<value>shipping_centers</value>
</option>
</constraint>
</property>
</class>
</constraint-mapping>

.. code-block:: php

// src/Entity/Student.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('promotion', new Assert\ExpressionSyntax());

$metadata->addPropertyConstraint('shippingOptions', new Assert\ExpressionSyntax([
'allowedVariables' => ['user', 'shipping_centers'],
]));
}
}

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.

.. include:: /reference/constraints/_groups-option.rst.inc

message
~~~~~~~

**type**: ``string`` **default**: ``This value should be a valid expression.``

This is the message displayed when the validation fails.

.. include:: /reference/constraints/_payload-option.rst.inc

.. _`ExpressionLanguage`: https://symfony.com/components/ExpressionLanguage
[8]ページ先頭
©2009-2025 Movatter.jp