Preserving and resetting state in code
<Editor key={ticket.id} ticket={ticket} />;Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 2
Topic
Preserving and resetting state
Definition
React preserves state by a component’s position in the render tree; changing type, position, or key can reset it.
In simpler words
State belongs to where a component sits in the UI, not to its function name alone.
Tree position, keys, remounting, and intentional resets.
After this you can
- Control whether a form retains or discards its local draft.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand Preserving and resetting state
Tree position, keys, remounting, and intentional resets.
Start by identifying which value or browser behavior changes. Then describe the UI from that current input instead of editing the DOM as a separate source of truth.
Apply Preserving and resetting state
Keep rendering as a calculation. Put user-triggered changes in event handlers, preserve UI memory in state, and reserve external synchronization for Effects or the server-state layer.
Name values by their UI meaning, test the loading and error path when data is remote, and avoid keeping two editable copies of the same value.
Ask before adding code: is this local UI memory, shared client state, or Nest-owned server state?
Where bugs hide
Definition
High-bug areas are places where a small API misuse looks correct but produces stale UI, duplicate work, or silent failures.
In simpler words
Each mistake below shows Wrong vs Right code — compare them side by side.
When something misbehaves, match the symptom to a pattern below before rewriting the feature.
Prefer fixing the ownership or update path over adding another Effect or sync step.
Mistake: Unstable key wiping drafts
// Wrong
<Editor key={Math.random()} ticket={ticket} />
// Right
<Editor key={ticket.id} ticket={ticket} />Stable keys preserve state; random keys remount.
Mistake: Expect state after type swap
// Wrong
{mode === "a" ? <Input /> : <TextArea />}
// expecting typed text to survive
// Right
// same component type, or lift the draft to the parentDifferent types remount and reset state.
Mistake: Same key, different entity
// Wrong
<Editor key="editor" ticket={ticket} />
// Right
<Editor key={ticket.id} ticket={ticket} />Key should change when the entity changes so drafts reset intentionally.
Live playground
Preserving and resetting state sandbox
Change one input at a time and predict the next render.
Changing key remounts the editor — local draft resets without manual clear.
Editing a1: (empty)
<TicketEditor key={ticket.id} ticketId={ticket.id} />Keep in mind
- Keep the formal definition in mind; it explains which tool belongs where.
- Prefer one source of truth over synchronized copies of the same value.
- When behavior surprises you, trace: input → update → render → committed UI.
- Study the Wrong vs Right examples in “Where bugs hide” before you merge.
Test
Check your understanding
At least 10 questions — mix of concept, syntax, practical, and logic. Score ≥ 80% (enforced by the API) to save progress.
Checking your session…
10 questions · concept 3 · syntax 3 · practical 2 · logic 2