Skip to content

docs: clarify this binding in setState callback #8414

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.

Sign up for GitHub

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
Assamee wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

docs: clarify this binding in setState callback #8414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 src/content/reference/react/Component.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -655,7 +655,7 @@ You don't have to do this, but it's handy if you want to update state multiple t
* If you pass an object as `nextState`, it will be shallowly merged into `this.state`.
* If you pass a function as `nextState`, it will be treated as an _updater function_. It must be pure, should take the pending state and props as arguments, and should return the object to be shallowly merged into `this.state`. React will put your updater function in a queue and re-render your component. During the next render, React will calculate the next state by applying all of the queued updaters to the previous state.

* **optional** `callback`: If specified, React will call the `callback` you've provided after the update is committed.
* **optional** `callback`: If specified, React will call the `callback` you've provided after the update is committed. React automatically binds the `this` keyword inside the callback to the current component.

#### Returns {/*setstate-returns*/}

Expand Down
Loading