Uh oh!
There was an error while loading. Please reload this page.
ReactDOM.flushSync(batch) - #10225
Merged
Merged
Conversation
4 tasks
acdlite
commented
Jul 21, 2017
CollaboratorAuthor
After some bikeshedding, we'll rename this to |
sebmarkbage
approved these changes
Jul 21, 2017
sebmarkbage
left a comment
Contributor
There was a problem hiding this comment.
Accepted pending the new name.
Contributor
There was a problem hiding this comment.
Should we kill syncUpdates and replace the calls with this flushSync?
Updates scheduled inside of activeUpdates are flushed by the end of the current tick. In async mode, this means updates are given sync priority. In sync mode, updates already have sync priority, so the effect of activeUpdates is to batch the updates together and flush them at the end of the batch. Unlike unstable_batchedUpdates, activeUpdates flushes at the end even if it's nested inside another batch.
Decided after much bikeshedding
Use flushSync instead.
6 tasks
5 tasks
mrizwanashiq pushed a commit
to mrizwanashiq/react
that referenced
this pull request
Jun 25, 2026
ReactDOM.flushSync(batch)
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updates scheduled inside of activeUpdates are flushed by the end of the current tick. In async mode, this means updates are given sync priority.
In sync mode, updates already have sync priority, so the effect of activeUpdates is to batch the updates together and flush them at the end of the batch.
Unlike unstable_batchedUpdates, activeUpdates flushes at the end even if it's nested inside another batch.