docs: clarify that mutationFn must await server sync before returning #492
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
createOptimisticAction'smutationFnmust ensure server writes have synced back before returningutils.refetch()to ensure synchronizationContext
The documentation previously didn't explain that inside your
mutationFn, you need to ensure that your server writes have synced back before you return. This is critical because the optimistic state is dropped when you return from a mutationFn.Users generally need to use collection-specific helpers to ensure sync, such as:
utils.refetch()utils.awaitTxId()Changes
docs/overview.mdwith the clarification and improved examplespackages/db/src/optimistic-action.ts(which generates the reference docs)Test plan
🤖 Generated with Claude Code