Skip to content

[ExpressionLanguage] Document the null-coalesce operator changes #19958

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
Jun 14, 2024
Merged

[ExpressionLanguage] Document the null-coalesce operator changes #19958

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
7 changes: 3 additions & 4 deletions reference/formats/expression_language.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,11 +124,10 @@ returns the right-hand side. Expressions can chain multiple coalescing operators
* ``foo[3] ?? 'no'``
* ``foo.baz ?? foo['baz'] ?? 'no'``

.. note::
.. versionadded:: 7.2

The main difference with the `null-coalescing operator in PHP`_ is that
ExpressionLanguage will throw an exception when trying to access a
non-existent variable.
Starting from Symfony 7.2, no exception is thrown when trying to access a
non-existent variable. This is the same behavior as the `null-coalescing operator in PHP`_.

.. _component-expression-functions:

Expand Down