From React DOCS:
https://reactjs.org/docs/state-and-lifecycle.html
State Updates May Be Asynchronous
React may batch multiple setState() calls into a single update for performance.
This makes total sense. If you have something like the function below, it would be very inefficient to re-render on every setState call
const [state1,setState1] = useState(false);
const [state2,setState2] = useState(false);
const [state3,setState3] = useState(false);
function handleClick() {
setState1(true);
setState2(true);
setState3(true);
}
So, in the situation above, I expect React to batch all 3 setState calls into a single re-render. And it does exactly that!
But what I want to know is:
Once handleClick has completed, is a re-render guaranteed to happen immediatelly handleClick has done running? I mean literally immediately, like synchronously immediately?
From this snippet that I've build, it seems that this is true. React will synchronously apply the updates (re-render) after handleClick has completed. Correct me if I'm wrong in assuming that.
See snippet below:
handleClick will call a setState and will log the current props.counter
App, so it will take a long time to re-renderprops.counter is different every time, without any repetition, even if you click multiple times really fasthandleClick function has already been recreated with the new value for props.counter that came from the counter updated state.QUESTION
When setState calls are made inside an event handler function, once that handler function has completed running, is it guaranteed that a re-render will occur immediately (synchronously) after that completion of the handler?
function App() {
console.log("App rendering...");
const [counter, setCounter] = React.useState(0);
// AN EXPENSIVE LOOP TO SLOW DOWN THE RENDER OF 'App'
for (let i = 0; i < 100000; ) {
for (let j = 0; j < 10000; j++) {}
i = i + 1;
}
return <Child counter={counter} setCounter={setCounter} />;
}
function Child(props) {
console.log("Child rendering...");
// THIS FUNCTION WILL CALL 'setState'
// AND WILL ALSO LOG THE CURRENT 'props.counter'
function handleClick() {
props.setCounter(prevState => prevState + 1);
console.log(props.counter);
}
return (
<React.Fragment>
<div>Counter: {props.counter}</div>
<button onClick={handleClick}>Click</button>
</React.Fragment>
);
}
const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.8.3/umd/react.production.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.8.3/umd/react-dom.production.min.js"></script>
<div id="root"/>
For new React developers, it is common to think that setState will trigger a re-render. But this is not always the case. If the value doesn't change, React will not trigger a re-render.
What happens when you call setState() inside render() method? Nothing happens.
⛔️ Re-renders reason: props changes (the big myth) In order for props to change, they need to be updated by the parent component. This means the parent would have to re-render, which will trigger re-render of the child component regardless of its props. Only when memoization techniques are used ( React.
The Standard React Component Will Call the Render Function Every Time Its Parents Re-Render. Let's have a look at this simple example. This is a simple counter app. Whenever the user clicks the “Up” button, the counter will increase by one and the app component gets re-rendered.
Once
handleClickhas completed, is a re-render guaranteed to happen immediatellyhandleClickhas done running? I mean literally immediately, like synchronously immediately
For certain events, including click, React guarantees that the component will be re-rendered before another event can occur. (This isn't the case for other events like mousemove.) You can find which events are which here. The current terminology seems to be that DiscreteEvents are the ones for which this guarantee exists, and the UserBlockingEvents are the ones for which it isn't guaranteed. It may well be that in the current implementation that means it's done synchronously at the end of the event handling¹, but I think the guarantee is less specific than that.
I learned this from Dan Abramov on Twitter (he used the older terminology for the events).
¹ Edit: and in fact, in his answer Joseph D. points to a comment by Dan Abramov saying that it is, for now, but also saying "This is implementation detail and may change in future versions".
is it guaranteed that a re-render will occur immediately (synchronously) after that completion of the handler?
Yes for onClick.
As pointed by Dan Abramov:
React batches all setStates done during a React event handler, and applies them just before exiting its own browser event handler.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With