useReducer for Complex Local Transitions Volume 06 - Professional Frontend | Phase 23
Reducer is not a global store useReducer is valuable when one local feature has several related transitions and scattered setters make the rules difficult to audit. It centralizes transition logic without changing state ownership.
Bulk selection example type SelectionState = { ids: Set<string> }
type Action = | { type: "toggle"; id: string } | { type: "replace"; ids: string[] } | { type: "clear" }
function selectionReducer( state: SelectionState, action: Action, ): SelectionState { // explicit transitions live here }
Use reducer when • Several events modify the same local state model.
• Transitions have invariants worth naming.
• You want pure transition tests.
• The state still belongs to one feature/component boundary.
Do not use reducer merely because • The component has more than one useState call.
• The data came from the server.
• You want to avoid learning the actual owner of the state.
useReducer for Complex Local Transitions matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “useReducer for Complex Local Transitions” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: value → owner → lifetime → source of truth → consumer. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: A state ownership map for TaskFlow plus refactored examples removing redundant synchronized state.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
API task rows -> TanStack Query
Search/filter URL -> URL/search params
Create form fields -> React Hook Form
Dialog open/closed -> local UI state
Authenticated user -> auth/session stateDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “useReducer for Complex Local Transitions” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Inventory every state variable on one TaskFlow screen and classify it: server, URL, form, local UI, or cross-cutting client.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.URL and React state disagreeing about filters
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.