Skip to content

[Validator] Update Expression constraint with "negate" option #16852

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2022
Merged

[Validator] Update Expression constraint with "negate" option #16852

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 18 additions & 0 deletions reference/constraints/Expression.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,13 @@ expression that must return true in order for validation to pass. To learn
more about the expression language syntax, see
:doc:`/components/expression_language/syntax`.

.. versionadded:: 6.2

The `negate` option was introduced in Symfony 6.2.

Alternatively, you can set the `negate` option to ``false`` in order to
assert that the expression must return ``true`` for validation to fail.

.. sidebar:: Mapping the Error to a Specific Field

You can also attach the constraint to a specific property and still validate
Expand Down Expand Up @@ -294,6 +301,17 @@ Parameter Description
``{{ label }}`` Corresponding form field label
=============== ==============================================================

``negate``
~~~~~~~~~~~

**type**: ``boolean`` **default**: ``true``

If ``false``, the validation fails when expression returns ``true``.

.. versionadded:: 6.2

The `negate` option was introduced in Symfony 6.2.

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

``values``
Expand Down