mutation invalidation
Query invalidation marks affected cached reads stale after a change.
Use this when A successful mutation leaves detail or list screens displaying old data.
without the term
“After I save a project, the list page still shows the old name until I refresh. Can you make the list and detail update after saving?”
with the term · How do you ask a model for mutation invalidation?
Invalidate the queries affected by this mutation. Verify updated detail and list views while unrelated queries remain reusable.
What is mutation invalidation?
After a write, you mark the cached reads it affected as stale so they refetch. Whether they refetch at once or on next use depends on the library and whether they are on screen.
Why does mutation invalidation matter when vibe coding?
Updating the server does not automatically update every client cache entry.
How do you do mutation invalidation?
Map the mutation to affected keys and verify active and inactive views.
What goes wrong with mutation invalidation?
Invalidating a plausible key that no actual reader uses.