Comments (2)
In React, when you update the state using useState
, React doesn't immediately update the state and re-render the component. Instead, it schedules the state update and re-rendering to occur asynchronously. This means that when you call setCount(1)
in your first scenario or setCount("2")
in your second scenario, React doesn't update the state and re-render the component immediately.
React batches state updates for performance reasons. When multiple setState
calls are made within the same synchronous event, React will batch them together and perform a single re-render at the end of the event. This is why you're seeing unexpected behavior in your console logs.
In your first scenario, when you click the button, React schedules the state update to 1, but before it re-renders the component, it logs the current count value, which is still 0. Then it re-renders the component with the updated count value of 1.
In your second scenario, similarly, React schedules the state update to "2" and logs the current count value, which is still "1" before re-rendering the component. Then it re-renders the component with the updated count value of "2".
This behavior is expected in React due to its asynchronous nature of state updates and re-renders. If you want to perform any action after the state has been updated, you should use useEffect
hook with appropriate dependencies.
But you can still try memoizing the state. However as far as I know this is expected behavior :)
const memoizedCount = useMemo(() => count, [count]);
from react.
In React, when you update the state using
useState
, React doesn't immediately update the state and re-render the component. Instead, it schedules the state update and re-rendering to occur asynchronously. This means that when you callsetCount(1)
in your first scenario orsetCount("2")
in your second scenario, React doesn't update the state and re-render the component immediately.React batches state updates for performance reasons. When multiple
setState
calls are made within the same synchronous event, React will batch them together and perform a single re-render at the end of the event. This is why you're seeing unexpected behavior in your console logs.In your first scenario, when you click the button, React schedules the state update to 1, but before it re-renders the component, it logs the current count value, which is still 0. Then it re-renders the component with the updated count value of 1.
In your second scenario, similarly, React schedules the state update to "2" and logs the current count value, which is still "1" before re-rendering the component. Then it re-renders the component with the updated count value of "2".
This behavior is expected in React due to its asynchronous nature of state updates and re-renders. If you want to perform any action after the state has been updated, you should use
useEffect
hook with appropriate dependencies.But you can still try memoizing the state. However as far as I know this is expected behavior :)
const memoizedCount = useMemo(() => count, [count]);
But I dont understand the async behaviour you mentioned. I know applying next rerender with new changes somehow asynchronus because of optimization. But I think it is not related with this. Because if you click once then wait for a minute, rerender will already be done and whereever the state value inside react closure should already be updated with next value until next click. Lets put some time between two clicks. React still rerender with same immutable value. Are you sure about your explanation? Other hand, I couldnt find any deep dive explanation about state closure implementation inside react. If you know implementation detail, please let me know.
from react.
Related Issues (20)
- Bug: Internal React error: Expected static flag was missing. HOT 3
- Bug: Additional updater function call is not ignored in Strict Mode HOT 1
- Bug: `react-hooks/rules-of-hooks` does not support `do/while` loops HOT 3
- Bug: React server components give type error in react 19 HOT 2
- Bug: Eager bailout when calling the state setter function multiple times HOT 4
- Bug: Multiple renderings in the same dom without being overwritten, all renders are displayed HOT 2
- Bug: React const function getting previous version of state value when calling the function. HOT 1
- Bug: Manually added event listener always triggered HOT 1
- donde verlo
- [DevTools Bug]: Canβt import chrome trace into react devtools HOT 2
- [DevTools Bug] Children cannot be added or removed during a reorder operation. HOT 1
- [DevTools Bug]: TypeError: ie.handlePostCommitFiberRoot is not a function HOT 3
- Hey really.org
- Bug: Invalid options to hydrateRoot can error with "This root received an early update" HOT 1
- Bug: `Children.map` raises error when passed async server component within client component HOT 4
- Bug: mouse events are bubbled up too far with some pointer-events rules HOT 1
- Bug: Unsupported HTML character references HOT 6
- Bug: React not defined in TypeScript when importing from npm HOT 8
- After using forwardRef in a JSX component, you encounter an error when using it in a TSX component. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react.