Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[ExpressionLanguage] Fix null-safe chaining#46454
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
nicolas-grekas left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
definitely a bugfix to me
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
b958c52 toe8479f9CompareHypeMC commentedMay 25, 2022
Made one minor change, I think it makes te code more readableee94071 |
Uh oh!
There was an error while loading.Please reload this page.
fabpot commentedMay 27, 2022
Thank you@HypeMC. |
d2f24e0 toa39c25cCompare
Uh oh!
There was an error while loading.Please reload this page.
Currently the null-safe operator in the expression language doesn't behave the same as in PHP. According to theRFC:
For example, in PHP the following expressions willreturn
null:This, however, is not the case with the null-safe operator in the expression language where the evaluation for such cases fails.
Not sure if this qualifies as a bug fix or a feature, so please let me know.