Distinguish between PUT/POST requests #17
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.
Description
Currently, when using this library with the Realtime Database, the
set()
function uses aPOST
request and thus inserts the provided data under a new key. Is this the intended behavior?I would have expected to set the data at the provided path (without new sub-key), ie using
PUT
.Example
Results in the following db entries:
Proposed changes
set()
toinsert()
set()
that usesPUT