fix(db): coerce async snapshot subscriptions with debounce operator #1588
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.
Checklist
yarn install
,yarn test
run successfully? yesDescription
Swaps
delay(0)
in favor ofdebounceTime(0)
to coerce asyncfromRef()
database snapshot subscriptions. This prevents asynclistChanges()
scans from burst emitting multiple copies of the sameref['on']('value')
events.@jamesdaniels Is this an acceptable / desirable change? It works well for me, but may have implications I'm not thinking of outside of standard RTDB use cases.
An alternative might be to revisit how
listChanges()
is implemented, perhaps by augmentingdistinctUntilChanged()
to debounce objects / arrays as well as immutable primitives.Code sample
src/database/observable/fromRef.ts