Skip to content

Commit f4fa2fc

Browse files
authored
Translate useState hook API (#341)
* WIP * Update chapter titles * WIP useState * Translate useState hook's API
1 parent 54056d9 commit f4fa2fc

File tree

8 files changed

+222
-221
lines changed

8 files changed

+222
-221
lines changed

beta/src/pages/apis/usereducer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ function reducer(state, action) {
185185
}
186186
```
187187
188-
Read [updating objects in state](/learn/updating-objects-in-state) and [updating arrays in state](/learn/updating-arrays-in-state) to learn more.
188+
Read [Aktualizowanie obiektów w stanie](/learn/updating-objects-in-state) and [Aktualizowanie tablic w stanie](/learn/updating-arrays-in-state) to learn more.
189189
190190
</Gotcha>
191191

beta/src/pages/apis/usestate.md

Lines changed: 209 additions & 208 deletions
Large diffs are not rendered by default.

beta/src/pages/learn/adding-interactivity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -401,7 +401,7 @@ Read **[Queueing a Series of State Changes](/learn/queueing-a-series-of-state-ch
401401

402402
</LearnMore>
403403

404-
## Updating objects in state {/*updating-objects-in-state*/}
404+
## Aktualizowanie obiektów w stanie {/*updating-objects-in-state*/}
405405

406406
State can hold any kind of JavaScript value, including objects. But you shouldn't change objects and arrays that you hold in the React state directly. Instead, when you want to update an object and array, you need to create a new one (or make a copy of an existing one), and then update the state to use that copy.
407407

@@ -628,11 +628,11 @@ img { width: 200px; height: 200px; }
628628

629629
<LearnMore path="/learn/updating-objects-in-state">
630630

631-
Read **[Updating Objects in State](/learn/updating-objects-in-state)** to learn how to update objects correctly.
631+
Read **[Aktualizowanie obiektów w stanie](/learn/updating-objects-in-state)** to learn how to update objects correctly.
632632

633633
</LearnMore>
634634

635-
## Updating arrays in state {/*updating-arrays-in-state*/}
635+
## Aktualizowanie tablic w stanie {/*updating-arrays-in-state*/}
636636

637637
Arrays are another type of mutable JavaScript objects you can store in state and should treat as read-only. 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:
638638

@@ -786,7 +786,7 @@ function ItemList({ artworks, onToggle }) {
786786

787787
<LearnMore path="/learn/updating-arrays-in-state">
788788

789-
Read **[Updating Arrays in State](/learn/updating-arrays-in-state)** to learn how to update arrays correctly.
789+
Read **[Aktualizowanie tablic w stanie](/learn/updating-arrays-in-state)** to learn how to update arrays correctly.
790790

791791
</LearnMore>
792792

beta/src/pages/learn/managing-state.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -300,7 +300,7 @@ Read **[Sharing State Between Components](/learn/sharing-state-between-component
300300
301301
</LearnMore>
302302
303-
## Preserving and resetting state {/*preserving-and-resetting-state*/}
303+
## Utrzymywanie i resetowanie stanu {/*preserving-and-resetting-state*/}
304304
305305
When you re-render a component, React needs to decide which parts of the tree to keep (and update), and which parts to discard or re-create from scratch. In most cases, React's automatic behavior works well enough. By default, React preserves the parts of the tree that "match up" with the previously rendered component tree.
306306

@@ -496,7 +496,7 @@ textarea {
496496

497497
<LearnMore path="/learn/preserving-and-resetting-state">
498498

499-
Read **[Preserving and Resetting State](/learn/preserving-and-resetting-state)** to learn the lifetime of state and how to control it.
499+
Read **[Utrzymywanie i resetowanie stanu](/learn/preserving-and-resetting-state)** to learn the lifetime of state and how to control it.
500500

501501
</LearnMore>
502502

beta/src/pages/learn/preserving-and-resetting-state.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Preserving and Resetting State
2+
title: Utrzymywanie i resetowanie stanu
33
---
44

55
<Intro>

beta/src/pages/learn/updating-arrays-in-state.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Updating Arrays in State
2+
title: Aktualizowanie tablic w stanie
33
---
44

55
<Intro>

beta/src/pages/learn/updating-objects-in-state.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Updating Objects in State
2+
title: Aktualizowanie obiektów w stanie
33
---
44

55
<Intro>

beta/src/sidebarLearn.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,11 +102,11 @@
102102
"path": "/learn/queueing-a-series-of-state-updates"
103103
},
104104
{
105-
"title": "Updating Objects in State",
105+
"title": "Aktualizowanie obiektów w stanie",
106106
"path": "/learn/updating-objects-in-state"
107107
},
108108
{
109-
"title": "Updating Arrays in State",
109+
"title": "Aktualizowanie tablic w stanie",
110110
"path": "/learn/updating-arrays-in-state"
111111
}
112112
]
@@ -131,7 +131,7 @@
131131
"path": "/learn/sharing-state-between-components"
132132
},
133133
{
134-
"title": "Preserving and Resetting State",
134+
"title": "Utrzymywanie i resetowanie stanu",
135135
"path": "/learn/preserving-and-resetting-state"
136136
},
137137
{

0 commit comments

Comments
 (0)