setState do? setState() schedules an update to a component’s state object. When state changes, the component responds by re-rendering.
state and props? props (short for “properties”) and state are both plain JavaScript objects. While both hold information that influences the output of render, they are different in one important way: props get passed to the component (similar to function parameters) whereas state is managed within the component (similar to variables declared within a function).
Here are some good resources for further reading on when to use props vs state:
setState giving me the wrong value? In React, both this.props and this.state represent the rendered values, i.e. what’s currently on the screen.
Calls to setState are asynchronous - don’t rely on this.state to reflect the new value immediately after calling setState. Pass an updater function instead of an object if you need to compute values based on the current state (see below for details).
Example of code that will not behave as expected:
\nincrementCount() {\n // Note: this will *not* work as intended.\n this.setState({count: this.state.count + 1});\n}\n\nhandleSomething() {\n // Let's say `this.state.count` starts at 0.\n this.incrementCount();\n this.incrementCount();\n this.incrementCount();\n // When React re-renders the component, `this.state.count` will be 1, but you expected 3.\n\n // This is because `incrementCount()` function above reads from `this.state.count`,\n // but React doesn't update `this.state.count` until the component is re-rendered.\n // So `incrementCount()` ends up reading `this.state.count` as 0 every time, and sets it to 1.\n\n // The fix is described below!\n}See below for how to fix this problem.
\nPass a function instead of an object to setState to ensure the call always uses the most updated version of state (see below).
setState? Passing an update function allows you to access the current state value inside the updater. Since setState calls are batched, this lets you chain updates and ensure they build on top of each other instead of conflicting:
incrementCount() {\n this.setState((state) => {\n // Important: read `state` instead of `this.state` when updating.\n return {count: state.count + 1}\n });\n}\n\nhandleSomething() {\n // Let's say `this.state.count` starts at 0.\n this.incrementCount();\n this.incrementCount();\n this.incrementCount();\n\n // If you read `this.state.count` now, it would still be 0.\n // But when React re-renders the component, it will be 3.\n}setState asynchronous? Currently, setState is asynchronous inside event handlers.
This ensures, for example, that if both Parent and Child call setState during a click event, Child isn’t re-rendered twice. Instead, React “flushes” the state updates at the end of the browser event. This results in significant performance improvements in larger apps.
This is an implementation detail so avoid relying on it directly. In the future versions, React will batch updates by default in more cases.
\nthis.state synchronously? As explained in the previous section, React intentionally “waits” until all components call setState() in their event handlers before starting to re-render. This boosts performance by avoiding unnecessary re-renders.
However, you might still be wondering why React doesn’t just update this.state immediately without re-rendering.
There are two main reasons:
\nprops and state, causing issues that are very hard to debug.This GitHub comment dives deep into the specific examples.
\nIt’s a good idea to get to know React first, before adding in additional libraries. You can build quite complex applications using only React.
","frontmatter":{"title":"Component State","next":null,"prev":null},"fields":{"path":"content/docs/faq-state.md","slug":"docs/faq-state.html"}}},"pageContext":{"slug":"docs/faq-state.html"}},"staticQueryHashes":[]}