Update README.md #155
Merged
Update README.md #155
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
If you `delete item['.key']`, then in the next line `this.$firebaseRefs.items.child(item['.key'])` means `this.$firebaseRefs.items.child(UNDEFINED)`
posva
approved these changes
Jan 27, 2018
|
@posva You're welcome! Actually I'm still playing around with it, and if I'm not mistaken, it's not even necessary to make a copy. As long as you delete the key, you can assign the same variable. Also now I know how to copy objects with the spread operator, that's a good one. 👍 |
|
Yes! It's just in case you use the |
posva
added a commit
that referenced
this pull request
Jul 10, 2018
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.
If you
delete item['.key'], then in the next linethis.$firebaseRefs.items.child(item['.key'])meansthis.$firebaseRefs.items.child(UNDEFINED)