Fix the example for the When constraint #17905
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When evaluating the expression, the ExpressionLanguage does not have access to private properties of the object, as it runs from its outside. And contrary to Twig, ExpressionLanguage does not have the magic `.` operator that tries to find a getter when it cannot use the property.
OskarStark
approved these changes
Feb 14, 2023
|
Thanks for fixing this bug @stof. |
kbond
added a commit
to symfony/ux
that referenced
this pull request
Jun 1, 2024
This PR was merged into the 2.x branch. Discussion ---------- Fix the example with Expression Language `@stof` said in symfony/symfony-docs#17905: > When evaluating the expression, the ExpressionLanguage does not have access to private properties of the object, as it runs from its outside. And contrary to Twig, ExpressionLanguage does not have the magic . operator that tries to find a getter when it cannot use the property. I then improved the documentation :). Commits ------- 15c6786 Fix the example with Expression Language
symfony-splitter
pushed a commit
to symfony/ux-turbo
that referenced
this pull request
Jun 1, 2024
This PR was merged into the 2.x branch. Discussion ---------- Fix the example with Expression Language `@stof` said in symfony/symfony-docs#17905: > When evaluating the expression, the ExpressionLanguage does not have access to private properties of the object, as it runs from its outside. And contrary to Twig, ExpressionLanguage does not have the magic . operator that tries to find a getter when it cannot use the property. I then improved the documentation :). Commits ------- 15c6786a Fix the example with Expression Language
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When evaluating the expression, the ExpressionLanguage does not have access to private properties of the object, as it runs from its outside. And contrary to Twig, ExpressionLanguage does not have the magic
.operator that tries to find a getter when it cannot use the property.See symfony/symfony#49367 for a support request caused by this bad example.