Optimistic Create and Temporary Identity Phase 25 - Optimistic Updates
Creating is different from updating An update already has a stable server identity. A create request may not. Inventing a fake database ID and inserting it into every cache can create difficult reconciliation bugs.
Preferred first approach For Task creation, TaskFlow initially uses UI optimism: render the pending mutation variables as a temporary row while the request is pending, then invalidate the Task list when the server returns.
Mutation state across components const pendingCreates = useMutationState({ filters: { mutationKey: ["tasks", "create"], status: "pending", }, select: mutation => ({ input: mutation.state.variables, submittedAt: mutation.state.submittedAt, }), })
Why submittedAt helps Multiple creates can be pending simultaneously. submittedAt gives each pending mutation a client-side rendering key without pretending it is the permanent Task ID.
When temporary IDs are justified Offline-first applications, drag/drop composition before sync, or complex local graph editing may justify a real client-generated temporary identity strategy. TaskFlow has not earned that complexity yet.
Optimistic Create and Temporary Identity 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 “Optimistic Create and Temporary Identity” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: user action → snapshot → optimistic cache → server result → commit/rollback. 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: Optimistic task update/create flow with rollback and authoritative server reconciliation.. 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.
onMutate: async (input) => {
await queryClient.cancelQueries({ queryKey: taskKeys.all });
const previous = queryClient.getQueryData(taskKeys.all);
applyOptimisticChange(input);
return { previous };
},
onError: (_err, _input, ctx) => restore(ctx?.previous),Do 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 “Optimistic Create and Temporary Identity” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Choose one mutation where low failure probability and UX benefit justify optimism.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Older mutation response overwriting newer user intent
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.