Fixes access on deeply nested, nonexistent property#1432
Merged
colerogers merged 8 commits intomasterfrom Jan 26, 2024
Merged
Conversation
|
We have recently upgraded to 4.4.1 and are facing the exact same issue after updating. |
colerogers
approved these changes
Jul 20, 2023
|
Any updates on this? It's preventing us to update to latest version |
|
Ping, is this stuck in limbo? |
This was referenced May 24, 2024
This was referenced Sep 6, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 attempting to access a deeply nested property on a RTDB node, we are currently throwing an error whereas the expected behavior is to return
null. This PR corrects the behavior.Fixes #1426.