[ExpressionLanguage] Fix null coalescing for object properties #49230
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
|
Hey! Thanks for your PR. You are targeting branch "6.3" but it seems your PR description refers to branch "6.2". Cheers! Carsonbot |
|
Hey! I think @mytuny has recently worked with this code. Maybe they can help review this? Cheers! Carsonbot |
carsonbot
changed the title
fancyweb
changed the title
|
I'm closing in favor of #47446 since it was opened before. |
|
Thanks for the warning. I also think the patch in the other PR is wrong so I proposed an alternative solution. Feel free to test it and review it 🙏 |
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.
Support deep object traversal that respects null coalescing operator
??, such as: