Itqualityassurance
When you directly update the state, it does not change this. state immediately. Instead, it creates a pending state transition, and accessing it after calling this method will only return the present value. You will lose control of the state across all components.
- Why can't we change state directly?
- Why don't we update state directly in React?
- Why state objects are not recommended to mutate directly?
- What happens if we change state directly in React?
Why can't we change state directly?
So, when you mutate the state directly and call setState() with an empty object. The previous state will be polluted with your mutation. Due to which, the shallow compare and merge of two states will be disturbed or won't happen, because you'll have only one state now.
Why don't we update state directly in React?
State updates in React are asynchronous; when an update is requested, there is no guarantee that the updates will be made immediately. The updater functions enqueue changes to the component state, but React may delay the changes, updating several components in a single pass.
Why state objects are not recommended to mutate directly?
Modifying the state directly will disturb this process. As a result the component will behave unexpectedly.
What happens if we change state directly in React?
The state of a component is managed internally by React. Updating the state of a component directly can have unintended consequences that can be difficult to debug. If the state is updated directly as in the example above, the component will not rerender since the state is compared shallowly.
