Skip to content

Documentation: State Updates May Be Asynchronous #3197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/docs/state-and-lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -342,7 +342,7 @@ The only place where you can assign `this.state` is the constructor.

React may batch multiple `setState()` calls into a single update for performance.

Because `this.props` and `this.state` may be updated asynchronously, you should not rely on their values for calculating the next state.
Because `this.props` and `this.state` may be updated asynchronously, i.e. eventually but not necessarily in the order you would expect, you should not rely on their values for calculating the next state.

For example, this code may fail to update the counter:

Expand Down