Queueing state updates in code
setCount(n => n + 1);
setCount(n => n + 1);
setCount(n => n + 1);Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 1
Topic
Queueing state updates
Definition
React queues state updates during an event and processes updater functions in order before the next render.
In simpler words
When the next value depends on the previous one, give React an updater function.
Batching, functional updaters, and replace versus update operations.
After this you can
- Apply several dependable updates in one event.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand Queueing state updates
Batching, functional updaters, and replace versus update operations.
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 Queueing state updates
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: Chained increments without updater
// Wrong
onClick={() => {
setN(n + 1);
setN(n + 1);
}}
// Right
onClick={() => {
setN(n => n + 1);
setN(n => n + 1);
}}Each updater receives the latest queued value.
Mistake: Async callback without updater
// Wrong
await save();
setN(n + 1); // n may be stale
// Right
await save();
setN(n => n + 1);After await, prefer functional updates.
Mistake: Assuming sync flush
// Wrong
setN(1);
expect(screen.getByText("1")); // same tick
// Right
// wait for next render in tests (findBy / waitFor)Updates are processed after the event handler finishes (batching).
Live playground
Queueing state updates sandbox
Change one input at a time and predict the next render.
Three setN(n + 1) with the same snapshot add 1. Functional updaters add 3.
setN(n + 1); setN(n + 1); setN(n + 1); // +1 setN(n => n + 1); // ×3 → +3
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