Fix act
not flushing effects/updates if global effect/update queues are non-empty before act
call
#1851
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.
When scheduling a state update or effect, check whether the
options.{debounceRendering, requestAnimationFrame}
hooks changed sincean update/effect queue flush was last scheduled and schedule a flush
using the new hooks if so.
This fixes an issue where a call to
act
would fail to synchronously flushstate updates and effects if a flush was already scheduled but not yet executed
before
act
was called. This happened because when a state update or effect wasqueued during the
act
callback, if the global update/effect queues werenon-empty then the temporary hooks installed by
act
to facilitatesynchronously flushing the queue would not be called.
More generally, this fixes an issue where any changes to the scheduling hooks
do not take effect until any already-scheduled flushes have happened.
Fixes #1794