Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes access on deeply nested, nonexistent property #1432

Merged
merged 8 commits into from
Jan 26, 2024

Conversation

blidd-google
Copy link
Contributor

@blidd-google blidd-google commented Jun 30, 2023

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.

@timothegenzmer
Copy link

We have recently upgraded to 4.4.1 and are facing the exact same issue after updating.
I would love to see this merged and releases.
This is currently preventing us from updating

@blidd-google blidd-google self-assigned this Jul 11, 2023
@bezysoftware
Copy link

Any updates on this? It's preventing us to update to latest version

@bezysoftware
Copy link

Ping, is this stuck in limbo?

@colerogers colerogers merged commit e6f5d89 into master Jan 26, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DataSnapshot.val() throws error for nested child which doesn't exist
4 participants