An Interest In:
Web News this Week
- April 17, 2024
- April 16, 2024
- April 15, 2024
- April 14, 2024
- April 13, 2024
- April 12, 2024
- April 11, 2024
A cure for React useState hell?
Do you ever find yourself in React useState hook hell?
Yeah, this good stuff:
import { useState } from "react";function EditCalendarEvent() { const [startDate, setStartDate] = useState(); const [endDate, setEndDate] = useState(); const [title, setTitle] = useState(""); const [description, setDescription] = useState(""); const [location, setLocation] = useState(); const [attendees, setAttendees] = useState([]); return ( <> <input value={title} onChange={(e) => setTitle(e.target.value)} /> {/* ... */} </> );}
The above is a component to update a calendar event. Sadly, it has a number of problems.
Besides not being easy on the eyes, there are no safeguards here. Theres nothing preventing you from choosing an end date thats before the start date, which makes no sense.
Theres also no guard for a title or description that is too long.
Sure, we could hold our breath and trust that everywhere were calling set*()
we will remember (or even know) to validate all of these things before writing to state, but I dont rest easy knowing things are just sitting in such an easy to break state.
There is a better alternative to useState
Did you know that there is an alternative state hook that is more powerful and easier to use than you might think?
Using useReducer, we could transform the above code, to just this:
import { useReducer } from "react";function EditCalendarEvent() { const [event, updateEvent] = useReducer( (prev, next) => { return { ...prev, ...next }; }, { title: "", description: "", attendees: [] } ); return ( <> <input value={title} onChange={(e) => updateEvent({ title: e.target.value })} /> {/* ... */} </> );}
The useReducer
hook helps you control transformations from state A to state B.
Now, you could say I can do that with useState too, see and point to some code like this:
import { useState } from "react";function EditCalendarEvent() { const [event, setEvent] = useState({ title: "", description: "", attendees: [], }); return ( <> <input value={title} onChange={(e) => setEvent({ ...event, title: e.target.value })} /> {/* ... */} </> );}
Though youd be right, theres one very important thing to consider here. Besides that this format still hopes that you always remember to spread on ...event
so you dont mess up by mutating the object directly (and subsequently causing React to not rerender as expected), it still misses out on the most critical benefit of useReducer
the ability to supply a function that controls state transitions.
Going back to using useReducer
, the only difference is you get an additional argument that is a function that can help us ensure that each state transition is safe and valid:
import { useReducer } from "react";function EditCalendarEvent() { const [event, updateEvent] = useReducer( (prev, next) => { const newEvent = { ...prev, ...next }; // Ensure that the start date is never after the end date if (newEvent.startDate > newEvent.endDate) { newEvent.endDate = newEvent.startDate; } // Ensure that the title is never more than 100 chars if (newEvent.title.length > 100) { newEvent.title = newEvent.title.substring(0, 100); } return newEvent; }, { title: "", description: "", attendees: [] } ); return ( <> <input value={title} onChange={(e) => updateEvent({ title: e.target.value })} /> {/* ... */} </> );}
This ability to prevent direct mutation of state gives us a major safety net, especially as our code grows in complexity over time.
You can use useReducer
virtually anywhere youd use useState
Maybe you have the world's simplest component, a basic counter, so you are using the useState
hook:
import { useState } from "react";function Counter() { const [count, setCount] = useState(0); return <button onClick={() => setCount(count + 1)}>Count is {count}</button>;}
But even in this small example, should count
be able to go infinitely high? Should it ever be negative?
Ok, maybe its not so conceivable how a negative value could be achieved here, but if we wanted to set a count limit, its trivial with useReducer
and we can have complete confidence that the state is always valid, regardless of where and how its written to.
import { useReducer } from "react";function Counter() { const [count, setCount] = useReducer((prev, next) => Math.min(0, 10), 0); return <button onClick={() => setCount(count + 1)}>Count is {count}</button>;}
(Optionally) Redux-ify things
As things get more complex, you could even opt to use a redux style action-based pattern as well.
Going back to our calendar event example, we could alternatively write it similar to the below:
import { useReducer } from "react";function EditCalendarEvent() { const [event, updateEvent] = useReducer( (state, action) => { const newEvent = { ...state }; switch (action.type) { case "updateTitle": newEvent.title = action.title; break; // More actions... } return newEvent; }, { title: "", description: "", attendees: [] } ); return ( <> <input value={title} onChange={(e) => updateEvent({ type: "updateTitle", title: "Hello" })} /> {/* ... */} </> );}
If you look up just about any docs or articles about useReducer
, they seem to imply this is the one and only way to use the hook.
But I want to impress upon you that this is just only one of many patterns you can use this hook for. While this is subjective, I am personally not a huge fan of Redux and this type of pattern. It has its merits, but I think once you want to start layering in new patterns for actions, Mobx, Zustand, or XState are preferable in my personal opinion.
That said, there is something elegant about being able to utilize this pattern without any additional dependencies, so Ill give people who love this format that.
Sharing reducers
One other nicety of useReducer
is it can be handy when child components need to update data managed by this hook. As opposed to having to pass several functions like you would when using useState
, you could just pass your reducer function down.
From an example in the React docs:
const TodosDispatch = React.createContext(null);function TodosApp() { // Note: `dispatch` won't change between re-renders const [todos, updateTodos] = useReducer(todosReducer); return ( <TodosDispatch.Provider value={updateTodos}> <DeepTree todos={todos} /> </TodosDispatch.Provider> );}
Then from the child:
function DeepChild(props) { // If we want to perform an action, we can get dispatch from context. const updateTodos = useContext(TodosDispatch); function handleClick() { updateTodos({ type: "add", text: "hello" }); } return <button onClick={handleClick}>Add todo</button>;}
This way you can not only have just one unified update function, but have safety guarantees that state updates triggered by child components conform to your requirements.
The common pitfall
It is important to keep in mind that you must always treat the state value of the useReducer
hook as immutable. A number of problems can occur if you accidentally mutate the object in your reducer function.
For instance, an example from the React docs:
function reducer(state, action) { switch (action.type) { case "incremented_age": { // Wrong: mutating existing object state.age++; return state; } case "changed_name": { // Wrong: mutating existing object state.name = action.nextName; return state; } // ... }}
and the fix:
function reducer(state, action) { switch (action.type) { case "incremented_age": { // Correct: creating a new object return { ...state, age: state.age + 1, }; } case "changed_name": { // Correct: creating a new object return { ...state, name: action.nextName, }; } // ... }}
If you find you are often running into this problem, you could enlist the help of a small library:
(Optional) Common pitfall solution: Immer
One very nifty library for ensuring immutable data, while having an elegant mutable DX, is Immer.
The use-immer package additionally provides a useImmerReducer
****function that allows you to make state transitions via direct mutation, but under the hood creates an immutable copy using Proxies in JavaScript.
import { useImmerReducer } from "use-immer";function reducer(draft, action) { switch (action.type) { case "increment": draft.count++; break; case "decrement": draft.count--; break; }}function Counter() { const [state, dispatch] = useImmerReducer(reducer, initialState); return ( <> Count: {state.count} <button onClick={() => dispatch({ type: "increment" })}>+</button> <button onClick={() => dispatch({ type: "decrement" })}>-</button> </> );}
This of course is completely optional, and only needed if this solves problems you are actively encoutering.
So when should I use useState
vs useReducer
?
Despite my enthusiasm for useReducer
, and pointing out the many places you *could*** use it, lets remember not to prematurely abstract.
In general, you are likely still fine using useState
. I would consider incrementally adopting useReducer
as your state and validation requirements begin to get more complex, warranting the additional effort.
Then, if you are adopting useReducer
for complex objects frequently, and often hit pitfalls around mutation, introducing Immer
could be worthwhile.
That, or if youve gotten to this point of state management complexity, you may want to look at some even more scalable solutions, such as Mobx, Zustand, or XState to meet your needs.
But dont forget, start simple, and add complexity only as needed.
Thank you, David
This post was inspired by David Khourshid, creator of XState as Stately, who opened my eyes to the possibilities of the useReducer
hook with his epic twitter thread:
Here's a fun React tip: `useReducer` is a better `useState`, and it's easier to adopt than you may think.
Group related values together and spread them in the reducer. Then, updating is just:
updateThing({ prop: newValue })
And there's even more benefits to `useReducer`...16:04 PM - 19 Dec 2022
About Me
Hi! I'm Steve, CEO of Builder.io.
We make a way to drag + drop with your components to create pages and other CMS content on your site or app, visually.
You may find it interesting or useful:
Original Link: https://dev.to/builderio/a-cure-for-react-usestate-hell-1ldi
Dev To
An online community for sharing and discovering great ideas, having debates, and making friendsMore About this Source Visit Dev To