From f1e1188efe0ee16f2cda24be92c8dc8c52d2d48d Mon Sep 17 00:00:00 2001 From: Nivaldo Farias Date: Mon, 20 Jan 2025 16:34:24 -0300 Subject: [PATCH] Translate `updating-arrays-in-state.md` to pt-br --- src/content/learn/updating-arrays-in-state.md | 1965 +---------------- 1 file changed, 9 insertions(+), 1956 deletions(-) diff --git a/src/content/learn/updating-arrays-in-state.md b/src/content/learn/updating-arrays-in-state.md index 61e4f4e2d..9d78d7c31 100644 --- a/src/content/learn/updating-arrays-in-state.md +++ b/src/content/learn/updating-arrays-in-state.md @@ -1,1972 +1,25 @@ --- -title: Updating Arrays in State +title: Atualizando Arrays no Estado --- -Arrays are mutable in JavaScript, but you should treat them as immutable when you store them in state. Just like with objects, when you want to update an array stored in state, you need to create a new one (or make a copy of an existing one), and then set state to use the new array. +Arrays são mutáveis em JavaScript, mas você deve tratá-los como imutáveis quando os armazena no estado. Assim como com objetos, quando você deseja atualizar um array armazenado no estado, precisa criar um novo (ou fazer uma cópia de um existente) e, em seguida, definir o estado para usar o novo array. -- How to add, remove, or change items in an array in React state -- How to update an object inside of an array -- How to make array copying less repetitive with Immer +- Como adicionar, remover ou alterar itens em um array no estado do React +- Como atualizar um objeto dentro de um array +- Como tornar a cópia de arrays menos repetitiva com Immer -## Updating arrays without mutation {/*updating-arrays-without-mutation*/} +## Atualizando arrays sem mutação {/*updating-arrays-without-mutation*/} -In JavaScript, arrays are just another kind of object. [Like with objects](/learn/updating-objects-in-state), **you should treat arrays in React state as read-only.** This means that you shouldn't reassign items inside an array like `arr[0] = 'bird'`, and you also shouldn't use methods that mutate the array, such as `push()` and `pop()`. +Em JavaScript, arrays são apenas mais um tipo de objeto. [Assim como com objetos](/learn/updating-objects-in-state), **você deve tratar arrays no estado do React como somente leitura.** Isso significa que você não deve reatribuir itens dentro de um array como `arr[0] = 'pássaro'`, e você também não deve usar métodos que mutam o array, como `push()` e `pop()`. -Instead, every time you want to update an array, you'll want to pass a *new* array to your state setting function. To do that, you can create a new array from the original array in your state by calling its non-mutating methods like `filter()` and `map()`. Then you can set your state to the resulting new array. +Em vez disso, toda vez que você quiser atualizar um array, deve passar um *novo* array para sua função de definição de estado. Para fazer isso, você pode criar um novo array a partir do array original em seu estado chamando seus métodos não mutantes, como `filter()` e `map()`. Então você pode definir o seu estado para o novo array resultante. -Here is a reference table of common array operations. When dealing with arrays inside React state, you will need to avoid the methods in the left column, and instead prefer the methods in the right column: - -| | avoid (mutates the array) | prefer (returns a new array) | -| --------- | ----------------------------------- | ------------------------------------------------------------------- | -| adding | `push`, `unshift` | `concat`, `[...arr]` spread syntax ([example](#adding-to-an-array)) | -| removing | `pop`, `shift`, `splice` | `filter`, `slice` ([example](#removing-from-an-array)) | -| replacing | `splice`, `arr[i] = ...` assignment | `map` ([example](#replacing-items-in-an-array)) | -| sorting | `reverse`, `sort` | copy the array first ([example](#making-other-changes-to-an-array)) | - -Alternatively, you can [use Immer](#write-concise-update-logic-with-immer) which lets you use methods from both columns. - - - -Unfortunately, [`slice`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice) and [`splice`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/splice) are named similarly but are very different: - -* `slice` lets you copy an array or a part of it. -* `splice` **mutates** the array (to insert or delete items). - -In React, you will be using `slice` (no `p`!) a lot more often because you don't want to mutate objects or arrays in state. [Updating Objects](/learn/updating-objects-in-state) explains what mutation is and why it's not recommended for state. - - - -### Adding to an array {/*adding-to-an-array*/} - -`push()` will mutate an array, which you don't want: - - - -```js -import { useState } from 'react'; - -let nextId = 0; - -export default function List() { - const [name, setName] = useState(''); - const [artists, setArtists] = useState([]); - - return ( - <> -

Inspiring sculptors:

- setName(e.target.value)} - /> - - - - ); -} -``` - -```css -button { margin-left: 5px; } -``` - -
- -Instead, create a *new* array which contains the existing items *and* a new item at the end. There are multiple ways to do this, but the easiest one is to use the `...` [array spread](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax#spread_in_array_literals) syntax: - -```js -setArtists( // Replace the state - [ // with a new array - ...artists, // that contains all the old items - { id: nextId++, name: name } // and one new item at the end - ] -); -``` - -Now it works correctly: - - - -```js -import { useState } from 'react'; - -let nextId = 0; - -export default function List() { - const [name, setName] = useState(''); - const [artists, setArtists] = useState([]); - - return ( - <> -

Inspiring sculptors:

- setName(e.target.value)} - /> - - - - ); -} -``` - -```css -button { margin-left: 5px; } -``` - -
- -The array spread syntax also lets you prepend an item by placing it *before* the original `...artists`: - -```js -setArtists([ - { id: nextId++, name: name }, - ...artists // Put old items at the end -]); -``` - -In this way, spread can do the job of both `push()` by adding to the end of an array and `unshift()` by adding to the beginning of an array. Try it in the sandbox above! - -### Removing from an array {/*removing-from-an-array*/} - -The easiest way to remove an item from an array is to *filter it out*. In other words, you will produce a new array that will not contain that item. To do this, use the `filter` method, for example: - - - -```js -import { useState } from 'react'; - -let initialArtists = [ - { id: 0, name: 'Marta Colvin Andrade' }, - { id: 1, name: 'Lamidi Olonade Fakeye'}, - { id: 2, name: 'Louise Nevelson'}, -]; - -export default function List() { - const [artists, setArtists] = useState( - initialArtists - ); - - return ( - <> -

Inspiring sculptors:

- - - ); -} -``` - -
- -Click the "Delete" button a few times, and look at its click handler. - -```js -setArtists( - artists.filter(a => a.id !== artist.id) -); -``` - -Here, `artists.filter(a => a.id !== artist.id)` means "create an array that consists of those `artists` whose IDs are different from `artist.id`". In other words, each artist's "Delete" button will filter _that_ artist out of the array, and then request a re-render with the resulting array. Note that `filter` does not modify the original array. - -### Transforming an array {/*transforming-an-array*/} - -If you want to change some or all items of the array, you can use `map()` to create a **new** array. The function you will pass to `map` can decide what to do with each item, based on its data or its index (or both). - -In this example, an array holds coordinates of two circles and a square. When you press the button, it moves only the circles down by 50 pixels. It does this by producing a new array of data using `map()`: - - - -```js -import { useState } from 'react'; - -let initialShapes = [ - { id: 0, type: 'circle', x: 50, y: 100 }, - { id: 1, type: 'square', x: 150, y: 100 }, - { id: 2, type: 'circle', x: 250, y: 100 }, -]; - -export default function ShapeEditor() { - const [shapes, setShapes] = useState( - initialShapes - ); - - function handleClick() { - const nextShapes = shapes.map(shape => { - if (shape.type === 'square') { - // No change - return shape; - } else { - // Return a new circle 50px below - return { - ...shape, - y: shape.y + 50, - }; - } - }); - // Re-render with the new array - setShapes(nextShapes); - } - - return ( - <> - - {shapes.map(shape => ( -
- ))} - - ); -} -``` - -```css -body { height: 300px; } -``` - - - -### Replacing items in an array {/*replacing-items-in-an-array*/} - -It is particularly common to want to replace one or more items in an array. Assignments like `arr[0] = 'bird'` are mutating the original array, so instead you'll want to use `map` for this as well. - -To replace an item, create a new array with `map`. Inside your `map` call, you will receive the item index as the second argument. Use it to decide whether to return the original item (the first argument) or something else: - - - -```js -import { useState } from 'react'; - -let initialCounters = [ - 0, 0, 0 -]; - -export default function CounterList() { - const [counters, setCounters] = useState( - initialCounters - ); - - function handleIncrementClick(index) { - const nextCounters = counters.map((c, i) => { - if (i === index) { - // Increment the clicked counter - return c + 1; - } else { - // The rest haven't changed - return c; - } - }); - setCounters(nextCounters); - } - - return ( -
    - {counters.map((counter, i) => ( -
  • - {counter} - -
  • - ))} -
- ); -} -``` - -```css -button { margin: 5px; } -``` - -
- -### Inserting into an array {/*inserting-into-an-array*/} - -Sometimes, you may want to insert an item at a particular position that's neither at the beginning nor at the end. To do this, you can use the `...` array spread syntax together with the `slice()` method. The `slice()` method lets you cut a "slice" of the array. To insert an item, you will create an array that spreads the slice _before_ the insertion point, then the new item, and then the rest of the original array. - -In this example, the Insert button always inserts at the index `1`: - - - -```js -import { useState } from 'react'; - -let nextId = 3; -const initialArtists = [ - { id: 0, name: 'Marta Colvin Andrade' }, - { id: 1, name: 'Lamidi Olonade Fakeye'}, - { id: 2, name: 'Louise Nevelson'}, -]; - -export default function List() { - const [name, setName] = useState(''); - const [artists, setArtists] = useState( - initialArtists - ); - - function handleClick() { - const insertAt = 1; // Could be any index - const nextArtists = [ - // Items before the insertion point: - ...artists.slice(0, insertAt), - // New item: - { id: nextId++, name: name }, - // Items after the insertion point: - ...artists.slice(insertAt) - ]; - setArtists(nextArtists); - setName(''); - } - - return ( - <> -

Inspiring sculptors:

- setName(e.target.value)} - /> - -
    - {artists.map(artist => ( -
  • {artist.name}
  • - ))} -
- - ); -} -``` - -```css -button { margin-left: 5px; } -``` - -
- -### Making other changes to an array {/*making-other-changes-to-an-array*/} - -There are some things you can't do with the spread syntax and non-mutating methods like `map()` and `filter()` alone. For example, you may want to reverse or sort an array. The JavaScript `reverse()` and `sort()` methods are mutating the original array, so you can't use them directly. - -**However, you can copy the array first, and then make changes to it.** - -For example: - - - -```js -import { useState } from 'react'; - -const initialList = [ - { id: 0, title: 'Big Bellies' }, - { id: 1, title: 'Lunar Landscape' }, - { id: 2, title: 'Terracotta Army' }, -]; - -export default function List() { - const [list, setList] = useState(initialList); - - function handleClick() { - const nextList = [...list]; - nextList.reverse(); - setList(nextList); - } - - return ( - <> - -
    - {list.map(artwork => ( -
  • {artwork.title}
  • - ))} -
- - ); -} -``` - -
- -Here, you use the `[...list]` spread syntax to create a copy of the original array first. Now that you have a copy, you can use mutating methods like `nextList.reverse()` or `nextList.sort()`, or even assign individual items with `nextList[0] = "something"`. - -However, **even if you copy an array, you can't mutate existing items _inside_ of it directly.** This is because copying is shallow--the new array will contain the same items as the original one. So if you modify an object inside the copied array, you are mutating the existing state. For example, code like this is a problem. - -```js -const nextList = [...list]; -nextList[0].seen = true; // Problem: mutates list[0] -setList(nextList); -``` - -Although `nextList` and `list` are two different arrays, **`nextList[0]` and `list[0]` point to the same object.** So by changing `nextList[0].seen`, you are also changing `list[0].seen`. This is a state mutation, which you should avoid! You can solve this issue in a similar way to [updating nested JavaScript objects](/learn/updating-objects-in-state#updating-a-nested-object)--by copying individual items you want to change instead of mutating them. Here's how. - -## Updating objects inside arrays {/*updating-objects-inside-arrays*/} - -Objects are not _really_ located "inside" arrays. They might appear to be "inside" in code, but each object in an array is a separate value, to which the array "points". This is why you need to be careful when changing nested fields like `list[0]`. Another person's artwork list may point to the same element of the array! - -**When updating nested state, you need to create copies from the point where you want to update, and all the way up to the top level.** Let's see how this works. - -In this example, two separate artwork lists have the same initial state. They are supposed to be isolated, but because of a mutation, their state is accidentally shared, and checking a box in one list affects the other list: - - - -```js -import { useState } from 'react'; - -let nextId = 3; -const initialList = [ - { id: 0, title: 'Big Bellies', seen: false }, - { id: 1, title: 'Lunar Landscape', seen: false }, - { id: 2, title: 'Terracotta Army', seen: true }, -]; - -export default function BucketList() { - const [myList, setMyList] = useState(initialList); - const [yourList, setYourList] = useState( - initialList - ); - - function handleToggleMyList(artworkId, nextSeen) { - const myNextList = [...myList]; - const artwork = myNextList.find( - a => a.id === artworkId - ); - artwork.seen = nextSeen; - setMyList(myNextList); - } - - function handleToggleYourList(artworkId, nextSeen) { - const yourNextList = [...yourList]; - const artwork = yourNextList.find( - a => a.id === artworkId - ); - artwork.seen = nextSeen; - setYourList(yourNextList); - } - - return ( - <> -

Art Bucket List

-

My list of art to see:

- -

Your list of art to see:

- - - ); -} - -function ItemList({ artworks, onToggle }) { - return ( -
    - {artworks.map(artwork => ( -
  • - -
  • - ))} -
- ); -} -``` - -
- -The problem is in code like this: - -```js -const myNextList = [...myList]; -const artwork = myNextList.find(a => a.id === artworkId); -artwork.seen = nextSeen; // Problem: mutates an existing item -setMyList(myNextList); -``` - -Although the `myNextList` array itself is new, the *items themselves* are the same as in the original `myList` array. So changing `artwork.seen` changes the *original* artwork item. That artwork item is also in `yourList`, which causes the bug. Bugs like this can be difficult to think about, but thankfully they disappear if you avoid mutating state. - -**You can use `map` to substitute an old item with its updated version without mutation.** - -```js -setMyList(myList.map(artwork => { - if (artwork.id === artworkId) { - // Create a *new* object with changes - return { ...artwork, seen: nextSeen }; - } else { - // No changes - return artwork; - } -})); -``` - -Here, `...` is the object spread syntax used to [create a copy of an object.](/learn/updating-objects-in-state#copying-objects-with-the-spread-syntax) - -With this approach, none of the existing state items are being mutated, and the bug is fixed: - - - -```js -import { useState } from 'react'; - -let nextId = 3; -const initialList = [ - { id: 0, title: 'Big Bellies', seen: false }, - { id: 1, title: 'Lunar Landscape', seen: false }, - { id: 2, title: 'Terracotta Army', seen: true }, -]; - -export default function BucketList() { - const [myList, setMyList] = useState(initialList); - const [yourList, setYourList] = useState( - initialList - ); - - function handleToggleMyList(artworkId, nextSeen) { - setMyList(myList.map(artwork => { - if (artwork.id === artworkId) { - // Create a *new* object with changes - return { ...artwork, seen: nextSeen }; - } else { - // No changes - return artwork; - } - })); - } - - function handleToggleYourList(artworkId, nextSeen) { - setYourList(yourList.map(artwork => { - if (artwork.id === artworkId) { - // Create a *new* object with changes - return { ...artwork, seen: nextSeen }; - } else { - // No changes - return artwork; - } - })); - } - - return ( - <> -

Art Bucket List

-

My list of art to see:

- -

Your list of art to see:

- - - ); -} - -function ItemList({ artworks, onToggle }) { - return ( -
    - {artworks.map(artwork => ( -
  • - -
  • - ))} -
- ); -} -``` - -
- -In general, **you should only mutate objects that you have just created.** If you were inserting a *new* artwork, you could mutate it, but if you're dealing with something that's already in state, you need to make a copy. - -### Write concise update logic with Immer {/*write-concise-update-logic-with-immer*/} - -Updating nested arrays without mutation can get a little bit repetitive. [Just as with objects](/learn/updating-objects-in-state#write-concise-update-logic-with-immer): - -- Generally, you shouldn't need to update state more than a couple of levels deep. If your state objects are very deep, you might want to [restructure them differently](/learn/choosing-the-state-structure#avoid-deeply-nested-state) so that they are flat. -- If you don't want to change your state structure, you might prefer to use [Immer](https://github.com/immerjs/use-immer), which lets you write using the convenient but mutating syntax and takes care of producing the copies for you. - -Here is the Art Bucket List example rewritten with Immer: - - - -```js -import { useState } from 'react'; -import { useImmer } from 'use-immer'; - -let nextId = 3; -const initialList = [ - { id: 0, title: 'Big Bellies', seen: false }, - { id: 1, title: 'Lunar Landscape', seen: false }, - { id: 2, title: 'Terracotta Army', seen: true }, -]; - -export default function BucketList() { - const [myList, updateMyList] = useImmer( - initialList - ); - const [yourList, updateYourList] = useImmer( - initialList - ); - - function handleToggleMyList(id, nextSeen) { - updateMyList(draft => { - const artwork = draft.find(a => - a.id === id - ); - artwork.seen = nextSeen; - }); - } - - function handleToggleYourList(artworkId, nextSeen) { - updateYourList(draft => { - const artwork = draft.find(a => - a.id === artworkId - ); - artwork.seen = nextSeen; - }); - } - - return ( - <> -

Art Bucket List

-

My list of art to see:

- -

Your list of art to see:

- - - ); -} - -function ItemList({ artworks, onToggle }) { - return ( -
    - {artworks.map(artwork => ( -
  • - -
  • - ))} -
- ); -} -``` - -```json package.json -{ - "dependencies": { - "immer": "1.7.3", - "react": "latest", - "react-dom": "latest", - "react-scripts": "latest", - "use-immer": "0.5.1" - }, - "scripts": { - "start": "react-scripts start", - "build": "react-scripts build", - "test": "react-scripts test --env=jsdom", - "eject": "react-scripts eject" - } -} -``` - -
- -Note how with Immer, **mutation like `artwork.seen = nextSeen` is now okay:** - -```js -updateMyTodos(draft => { - const artwork = draft.find(a => a.id === artworkId); - artwork.seen = nextSeen; -}); -``` - -This is because you're not mutating the _original_ state, but you're mutating a special `draft` object provided by Immer. Similarly, you can apply mutating methods like `push()` and `pop()` to the content of the `draft`. - -Behind the scenes, Immer always constructs the next state from scratch according to the changes that you've done to the `draft`. This keeps your event handlers very concise without ever mutating state. - - - -- You can put arrays into state, but you can't change them. -- Instead of mutating an array, create a *new* version of it, and update the state to it. -- You can use the `[...arr, newItem]` array spread syntax to create arrays with new items. -- You can use `filter()` and `map()` to create new arrays with filtered or transformed items. -- You can use Immer to keep your code concise. - - - - - - - -#### Update an item in the shopping cart {/*update-an-item-in-the-shopping-cart*/} - -Fill in the `handleIncreaseClick` logic so that pressing "+" increases the corresponding number: - - - -```js -import { useState } from 'react'; - -const initialProducts = [{ - id: 0, - name: 'Baklava', - count: 1, -}, { - id: 1, - name: 'Cheese', - count: 5, -}, { - id: 2, - name: 'Spaghetti', - count: 2, -}]; - -export default function ShoppingCart() { - const [ - products, - setProducts - ] = useState(initialProducts) - - function handleIncreaseClick(productId) { - - } - - return ( -
    - {products.map(product => ( -
  • - {product.name} - {' '} - ({product.count}) - -
  • - ))} -
- ); -} -``` - -```css -button { margin: 5px; } -``` - -
- - - -You can use the `map` function to create a new array, and then use the `...` object spread syntax to create a copy of the changed object for the new array: - - - -```js -import { useState } from 'react'; - -const initialProducts = [{ - id: 0, - name: 'Baklava', - count: 1, -}, { - id: 1, - name: 'Cheese', - count: 5, -}, { - id: 2, - name: 'Spaghetti', - count: 2, -}]; - -export default function ShoppingCart() { - const [ - products, - setProducts - ] = useState(initialProducts) - - function handleIncreaseClick(productId) { - setProducts(products.map(product => { - if (product.id === productId) { - return { - ...product, - count: product.count + 1 - }; - } else { - return product; - } - })) - } - - return ( -
    - {products.map(product => ( -
  • - {product.name} - {' '} - ({product.count}) - -
  • - ))} -
- ); -} -``` - -```css -button { margin: 5px; } -``` - -
- -
- -#### Remove an item from the shopping cart {/*remove-an-item-from-the-shopping-cart*/} - -This shopping cart has a working "+" button, but the "–" button doesn't do anything. You need to add an event handler to it so that pressing it decreases the `count` of the corresponding product. If you press "–" when the count is 1, the product should automatically get removed from the cart. Make sure it never shows 0. - - - -```js -import { useState } from 'react'; - -const initialProducts = [{ - id: 0, - name: 'Baklava', - count: 1, -}, { - id: 1, - name: 'Cheese', - count: 5, -}, { - id: 2, - name: 'Spaghetti', - count: 2, -}]; - -export default function ShoppingCart() { - const [ - products, - setProducts - ] = useState(initialProducts) - - function handleIncreaseClick(productId) { - setProducts(products.map(product => { - if (product.id === productId) { - return { - ...product, - count: product.count + 1 - }; - } else { - return product; - } - })) - } - - return ( -
    - {products.map(product => ( -
  • - {product.name} - {' '} - ({product.count}) - - -
  • - ))} -
- ); -} -``` - -```css -button { margin: 5px; } -``` - -
- - - -You can first use `map` to produce a new array, and then `filter` to remove products with a `count` set to `0`: - - - -```js -import { useState } from 'react'; - -const initialProducts = [{ - id: 0, - name: 'Baklava', - count: 1, -}, { - id: 1, - name: 'Cheese', - count: 5, -}, { - id: 2, - name: 'Spaghetti', - count: 2, -}]; - -export default function ShoppingCart() { - const [ - products, - setProducts - ] = useState(initialProducts) - - function handleIncreaseClick(productId) { - setProducts(products.map(product => { - if (product.id === productId) { - return { - ...product, - count: product.count + 1 - }; - } else { - return product; - } - })) - } - - function handleDecreaseClick(productId) { - let nextProducts = products.map(product => { - if (product.id === productId) { - return { - ...product, - count: product.count - 1 - }; - } else { - return product; - } - }); - nextProducts = nextProducts.filter(p => - p.count > 0 - ); - setProducts(nextProducts) - } - - return ( -
    - {products.map(product => ( -
  • - {product.name} - {' '} - ({product.count}) - - -
  • - ))} -
- ); -} -``` - -```css -button { margin: 5px; } -``` - -
- -
- -#### Fix the mutations using non-mutative methods {/*fix-the-mutations-using-non-mutative-methods*/} - -In this example, all of the event handlers in `App.js` use mutation. As a result, editing and deleting todos doesn't work. Rewrite `handleAddTodo`, `handleChangeTodo`, and `handleDeleteTodo` to use the non-mutative methods: - - - -```js src/App.js -import { useState } from 'react'; -import AddTodo from './AddTodo.js'; -import TaskList from './TaskList.js'; - -let nextId = 3; -const initialTodos = [ - { id: 0, title: 'Buy milk', done: true }, - { id: 1, title: 'Eat tacos', done: false }, - { id: 2, title: 'Brew tea', done: false }, -]; - -export default function TaskApp() { - const [todos, setTodos] = useState( - initialTodos - ); - - function handleAddTodo(title) { - todos.push({ - id: nextId++, - title: title, - done: false - }); - } - - function handleChangeTodo(nextTodo) { - const todo = todos.find(t => - t.id === nextTodo.id - ); - todo.title = nextTodo.title; - todo.done = nextTodo.done; - } - - function handleDeleteTodo(todoId) { - const index = todos.findIndex(t => - t.id === todoId - ); - todos.splice(index, 1); - } - - return ( - <> - - - - ); -} -``` - -```js src/AddTodo.js -import { useState } from 'react'; - -export default function AddTodo({ onAddTodo }) { - const [title, setTitle] = useState(''); - return ( - <> - setTitle(e.target.value)} - /> - - - ) -} -``` - -```js src/TaskList.js -import { useState } from 'react'; - -export default function TaskList({ - todos, - onChangeTodo, - onDeleteTodo -}) { - return ( -
    - {todos.map(todo => ( -
  • - -
  • - ))} -
- ); -} - -function Task({ todo, onChange, onDelete }) { - const [isEditing, setIsEditing] = useState(false); - let todoContent; - if (isEditing) { - todoContent = ( - <> - { - onChange({ - ...todo, - title: e.target.value - }); - }} /> - - - ); - } else { - todoContent = ( - <> - {todo.title} - - - ); - } - return ( - - ); -} -``` - -```css -button { margin: 5px; } -li { list-style-type: none; } -ul, li { margin: 0; padding: 0; } -``` - -
- - - -In `handleAddTodo`, you can use the array spread syntax. In `handleChangeTodo`, you can create a new array with `map`. In `handleDeleteTodo`, you can create a new array with `filter`. Now the list works correctly: - - - -```js src/App.js -import { useState } from 'react'; -import AddTodo from './AddTodo.js'; -import TaskList from './TaskList.js'; - -let nextId = 3; -const initialTodos = [ - { id: 0, title: 'Buy milk', done: true }, - { id: 1, title: 'Eat tacos', done: false }, - { id: 2, title: 'Brew tea', done: false }, -]; - -export default function TaskApp() { - const [todos, setTodos] = useState( - initialTodos - ); - - function handleAddTodo(title) { - setTodos([ - ...todos, - { - id: nextId++, - title: title, - done: false - } - ]); - } - - function handleChangeTodo(nextTodo) { - setTodos(todos.map(t => { - if (t.id === nextTodo.id) { - return nextTodo; - } else { - return t; - } - })); - } - - function handleDeleteTodo(todoId) { - setTodos( - todos.filter(t => t.id !== todoId) - ); - } - - return ( - <> - - - - ); -} -``` - -```js src/AddTodo.js -import { useState } from 'react'; - -export default function AddTodo({ onAddTodo }) { - const [title, setTitle] = useState(''); - return ( - <> - setTitle(e.target.value)} - /> - - - ) -} -``` - -```js src/TaskList.js -import { useState } from 'react'; - -export default function TaskList({ - todos, - onChangeTodo, - onDeleteTodo -}) { - return ( -
    - {todos.map(todo => ( -
  • - -
  • - ))} -
- ); -} - -function Task({ todo, onChange, onDelete }) { - const [isEditing, setIsEditing] = useState(false); - let todoContent; - if (isEditing) { - todoContent = ( - <> - { - onChange({ - ...todo, - title: e.target.value - }); - }} /> - - - ); - } else { - todoContent = ( - <> - {todo.title} - - - ); - } - return ( - - ); -} -``` - -```css -button { margin: 5px; } -li { list-style-type: none; } -ul, li { margin: 0; padding: 0; } -``` - -
- -
- - -#### Fix the mutations using Immer {/*fix-the-mutations-using-immer*/} - -This is the same example as in the previous challenge. This time, fix the mutations by using Immer. For your convenience, `useImmer` is already imported, so you need to change the `todos` state variable to use it. - - - -```js src/App.js -import { useState } from 'react'; -import { useImmer } from 'use-immer'; -import AddTodo from './AddTodo.js'; -import TaskList from './TaskList.js'; - -let nextId = 3; -const initialTodos = [ - { id: 0, title: 'Buy milk', done: true }, - { id: 1, title: 'Eat tacos', done: false }, - { id: 2, title: 'Brew tea', done: false }, -]; - -export default function TaskApp() { - const [todos, setTodos] = useState( - initialTodos - ); - - function handleAddTodo(title) { - todos.push({ - id: nextId++, - title: title, - done: false - }); - } - - function handleChangeTodo(nextTodo) { - const todo = todos.find(t => - t.id === nextTodo.id - ); - todo.title = nextTodo.title; - todo.done = nextTodo.done; - } - - function handleDeleteTodo(todoId) { - const index = todos.findIndex(t => - t.id === todoId - ); - todos.splice(index, 1); - } - - return ( - <> - - - - ); -} -``` - -```js src/AddTodo.js -import { useState } from 'react'; - -export default function AddTodo({ onAddTodo }) { - const [title, setTitle] = useState(''); - return ( - <> - setTitle(e.target.value)} - /> - - - ) -} -``` - -```js src/TaskList.js -import { useState } from 'react'; - -export default function TaskList({ - todos, - onChangeTodo, - onDeleteTodo -}) { - return ( -
    - {todos.map(todo => ( -
  • - -
  • - ))} -
- ); -} - -function Task({ todo, onChange, onDelete }) { - const [isEditing, setIsEditing] = useState(false); - let todoContent; - if (isEditing) { - todoContent = ( - <> - { - onChange({ - ...todo, - title: e.target.value - }); - }} /> - - - ); - } else { - todoContent = ( - <> - {todo.title} - - - ); - } - return ( - - ); -} -``` - -```css -button { margin: 5px; } -li { list-style-type: none; } -ul, li { margin: 0; padding: 0; } -``` - -```json package.json -{ - "dependencies": { - "immer": "1.7.3", - "react": "latest", - "react-dom": "latest", - "react-scripts": "latest", - "use-immer": "0.5.1" - }, - "scripts": { - "start": "react-scripts start", - "build": "react-scripts build", - "test": "react-scripts test --env=jsdom", - "eject": "react-scripts eject" - } -} -``` - -
- - - -With Immer, you can write code in the mutative fashion, as long as you're only mutating parts of the `draft` that Immer gives you. Here, all mutations are performed on the `draft` so the code works: - - - -```js src/App.js -import { useState } from 'react'; -import { useImmer } from 'use-immer'; -import AddTodo from './AddTodo.js'; -import TaskList from './TaskList.js'; - -let nextId = 3; -const initialTodos = [ - { id: 0, title: 'Buy milk', done: true }, - { id: 1, title: 'Eat tacos', done: false }, - { id: 2, title: 'Brew tea', done: false }, -]; - -export default function TaskApp() { - const [todos, updateTodos] = useImmer( - initialTodos - ); - - function handleAddTodo(title) { - updateTodos(draft => { - draft.push({ - id: nextId++, - title: title, - done: false - }); - }); - } - - function handleChangeTodo(nextTodo) { - updateTodos(draft => { - const todo = draft.find(t => - t.id === nextTodo.id - ); - todo.title = nextTodo.title; - todo.done = nextTodo.done; - }); - } - - function handleDeleteTodo(todoId) { - updateTodos(draft => { - const index = draft.findIndex(t => - t.id === todoId - ); - draft.splice(index, 1); - }); - } - - return ( - <> - - - - ); -} -``` - -```js src/AddTodo.js -import { useState } from 'react'; - -export default function AddTodo({ onAddTodo }) { - const [title, setTitle] = useState(''); - return ( - <> - setTitle(e.target.value)} - /> - - - ) -} -``` - -```js src/TaskList.js -import { useState } from 'react'; - -export default function TaskList({ - todos, - onChangeTodo, - onDeleteTodo -}) { - return ( -
    - {todos.map(todo => ( -
  • - -
  • - ))} -
- ); -} - -function Task({ todo, onChange, onDelete }) { - const [isEditing, setIsEditing] = useState(false); - let todoContent; - if (isEditing) { - todoContent = ( - <> - { - onChange({ - ...todo, - title: e.target.value - }); - }} /> - - - ); - } else { - todoContent = ( - <> - {todo.title} - - - ); - } - return ( - - ); -} -``` - -```css -button { margin: 5px; } -li { list-style-type: none; } -ul, li { margin: 0; padding: 0; } -``` - -```json package.json -{ - "dependencies": { - "immer": "1.7.3", - "react": "latest", - "react-dom": "latest", - "react-scripts": "latest", - "use-immer": "0.5.1" - }, - "scripts": { - "start": "react-scripts start", - "build": "react-scripts build", - "test": "react-scripts test --env=jsdom", - "eject": "react-scripts eject" - } -} -``` - -
- -You can also mix and match the mutative and non-mutative approaches with Immer. - -For example, in this version `handleAddTodo` is implemented by mutating the Immer `draft`, while `handleChangeTodo` and `handleDeleteTodo` use the non-mutative `map` and `filter` methods: - - - -```js src/App.js -import { useState } from 'react'; -import { useImmer } from 'use-immer'; -import AddTodo from './AddTodo.js'; -import TaskList from './TaskList.js'; - -let nextId = 3; -const initialTodos = [ - { id: 0, title: 'Buy milk', done: true }, - { id: 1, title: 'Eat tacos', done: false }, - { id: 2, title: 'Brew tea', done: false }, -]; - -export default function TaskApp() { - const [todos, updateTodos] = useImmer( - initialTodos - ); - - function handleAddTodo(title) { - updateTodos(draft => { - draft.push({ - id: nextId++, - title: title, - done: false - }); - }); - } - - function handleChangeTodo(nextTodo) { - updateTodos(todos.map(todo => { - if (todo.id === nextTodo.id) { - return nextTodo; - } else { - return todo; - } - })); - } - - function handleDeleteTodo(todoId) { - updateTodos( - todos.filter(t => t.id !== todoId) - ); - } - - return ( - <> - - - - ); -} -``` - -```js src/AddTodo.js -import { useState } from 'react'; - -export default function AddTodo({ onAddTodo }) { - const [title, setTitle] = useState(''); - return ( - <> - setTitle(e.target.value)} - /> - - - ) -} -``` - -```js src/TaskList.js -import { useState } from 'react'; - -export default function TaskList({ - todos, - onChangeTodo, - onDeleteTodo -}) { - return ( -
    - {todos.map(todo => ( -
  • - -
  • - ))} -
- ); -} - -function Task({ todo, onChange, onDelete }) { - const [isEditing, setIsEditing] = useState(false); - let todoContent; - if (isEditing) { - todoContent = ( - <> - { - onChange({ - ...todo, - title: e.target.value - }); - }} /> - - - ); - } else { - todoContent = ( - <> - {todo.title} - - - ); - } - return ( - - ); -} -``` - -```css -button { margin: 5px; } -li { list-style-type: none; } -ul, li { margin: 0; padding: 0; } -``` - -```json package.json -{ - "dependencies": { - "immer": "1.7.3", - "react": "latest", - "react-dom": "latest", - "react-scripts": "latest", - "use-immer": "0.5.1" - }, - "scripts": { - "start": "react-scripts start", - "build": "react-scripts build", - "test": "react-scripts test --env=jsdom", - "eject": "react-scripts eject" - } -} -``` - -
- -With Immer, you can pick the style that feels the most natural for each separate case. - -
- -
+Aqui está uma \ No newline at end of file