✳flâneur — a map of the web's best reading

Updating Objects in State – React

react.dev · 3,785 words · saved by 1 readers

State can hold any kind of JavaScript value, including objects. But you shouldn’t change objects that you hold in the React state directly. Instead, when you want to update an object, you need to create a new one (or make a copy of an existing one), and then set the state to use that copy. You can store any kind of JavaScript value in state. So far you’ve been working with numbers, strings, and booleans. These kinds of JavaScript values are “immutable”, meaning unchangeable or “read-only”. You can trigger a re-render to replace a value: The x state changed from 0 to 5, but the number 0 itself did not change. It’s not possible to make any changes to the built-in primitive values like numbers, strings, and booleans in JavaScript. Now consider an object in state: Technically, it is possible to change the contents of the object itself. This is called a mutation: However, although objects in React state are technically mutable, you should treat them as if they were immutable—like numbers, b

Learn React Adding Interactivity Copy page Copy Updating Objects in State State can hold any kind of JavaScript value, including objects. But you shouldn’t change objects that you hold in the React state directly. Instead, when you want to update an object, you need to create a new one (or make a copy of an existing one), and then set the state to use that copy. You will learn How to correctly update an object in React state How to update a nested object without mutating it What immutability is, and how not to break it How to make object copying less repetitive with Immer What’s a mutation? Yo

Explore this link on the map →

saved by

related reading