This content originally appeared on DEV Community 👩‍💻👨‍💻 and was authored by Isabelle M.
In React, hooks are a way to use state and other React features without having to generate a class component. One of the most frequently used hook is useState(), however on occasion useRef() might be a better and more efficient way to manage state.
A common use case is handling a form input field when the submit button is clicked. For example, lets look at the following code snippet:
const [email, setEmail] = useState('');
const [password, setPassword] = useState('');
const handleSubmit = (e) => {
e.preventDefault();
console.log(email, password);
};
return (
<form onSubmit={handleSubmit}>
<input
type="email"
value={email}
onChange={(e) => setEmail(e.target.value)}
/>
<input
type="password"
value={password}
onChange={(e) => setPassword(e.target.value)}
/>
<button type="submit">Submit</button>
</form>
);
In the above example, we have two input fields, one for the email and one for the password. When the submit button is clicked, the values of the two input fields are logged to the console. The useState() hook is used to manage the state of the two input fields. Although, this code does what it's supposed to do, it also causes the component to re-render every time the input fields are changed.
This is due to the usage of the useState() hook, which by definition causes the component to re-render every time the state is changed. This is not a problem in this example, but in a more complex application, this can cause performance issues. To avoid this, we can use the useRef() hook instead of useState().
const email = useRef('');
const password = useRef('');
const handleSubmit = (e) => {
e.preventDefault();
console.log(email.current, password.current);
};
return (
<form onSubmit={handleSubmit}>
<input
type="email"
value={email.current}
onChange={(e) => (email.current = e.target.value)}
/>
<input
type="password"
value={password.current}
onChange={(e) => (password.current = e.target.value)}
/>
<button type="submit">Submit</button>
</form>
);
When to use useRef() instead of useState()
A rule of thumb is to use useState when you need to re-render the component when the state changes and useRef when you don't need to re-render the component when the state changes.
Here are some examples of when to use useRef instead of useState:
- When you need to store a value that does not trigger a re-render when it is updated.
- When you need to store a value that is not used in the render method.
- When you need to store a value that persists for the lifetime of the component.
This content originally appeared on DEV Community 👩‍💻👨‍💻 and was authored by Isabelle M.
Isabelle M. | Sciencx (2022-11-26T22:00:00+00:00) When to use useRef() instead of useState(). Retrieved from https://www.scien.cx/2022/11/26/when-to-use-useref-instead-of-usestate/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.