State as a snapshot in code
function handleClick() {
setCount(count + 1);
console.log(count); // current snapshot
}Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 1
Topic
State as a snapshot
Definition
Each render receives a fixed snapshot of state values for that render’s event handlers and JSX.
In simpler words
A handler sees the state from the render that created it, even after it asks React for an update.
Snapshot semantics, closures, and scheduled renders.
After this you can
- Avoid expecting a state variable to change halfway through a handler.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand State as a snapshot
Snapshot semantics, closures, and scheduled renders.
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 State as a snapshot
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: Expecting setState to mutate immediately
// Wrong
setCount(count + 1);
console.log(count); // still old
// Right
setCount(count + 1);
// read new value on the next render / in updaterState is a snapshot for this render.
Mistake: Three +1 with same snapshot
// Wrong
setCount(count + 1);
setCount(count + 1);
setCount(count + 1); // +1 total
// Right
setCount(c => c + 1);
setCount(c => c + 1);
setCount(c => c + 1); // +3Use functional updaters when chaining.
Mistake: Stale timeout closure
// Wrong
setTimeout(() => setCount(count + 1), 1000);
// Right
setTimeout(() => setCount(c => c + 1), 1000);Updaters avoid capturing an old count.
Live playground
State as a snapshot sandbox
Change one input at a time and predict the next render.
State is a snapshot. Logging right after setState still sees the old value.
Rendered count: 0
—
setCount(count + 1); console.log(count); // previous snapshot
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