docs: Clarify potential gotcha when overriding serialize in rtdb #1083
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.
TLDR: The rtdb
childRemoved
handler usesindexForKey
to find the element to delete. This function assumes that a.key
property is defined on objects, which won't be the case if you override theserialize
option. This can lead to bugs when removing from array.For example, I had the following, which doesn't define
.key
:With this code, whenever I deleted an element from my array, it was always the last one that got removed. Took me a bit of time to figure out why deletion wasn't working, hence this documentation improvement.
The reason is that if
.key
is not defined,indexForKey
will return -1 which ultimately will gets passed to Array.slice which ends up removing the last item.A better fix might be to throw an error instead of returning -1 in
indexForKey
. Happy to work on this if that's deemed better.