fix: Make rtdb ref.push() only create local node when no value is passed#739
Open
jonathanedey wants to merge 8 commits intomainfrom
Open
fix: Make rtdb ref.push() only create local node when no value is passed#739jonathanedey wants to merge 8 commits intomainfrom
ref.push() only create local node when no value is passed#739jonathanedey wants to merge 8 commits intomainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The optional value argument in push() can be used to provide an initial value for the child node. If no value is provided, child node will have an empty string as the default value.
This behaviour was inconsistent with the client SDKs. If no value is provided, push() should now return a reference that can be used elsewhere and should not create an empty node on the server.