mis-client-crud-state

Patch the local store that owns the collection using the mutation response or submitted input. Prepend new rows on create, merge fields with map on update, and filter out the id on delete, avoiding any refetch call.

Track in-flight state keyed by the row's stable id in the shared store, not a global isPending flag. The row renders a spinner with reduced opacity and disabled interactions until the mutation resolves and the marker clears.

Refetch only when the server derives opaque fields like counts, permissions, or sort keys that the client cannot compute, or when multi-tab consistency is critical. Even then, prefer a scoped refetch of one item or one scope.

Avoid optimistic patching before the API call for deletes unless you implement rollback. The safer pattern keeps the row visible with an in-flight spinner and removes it from state only after the DELETE succeeds.

The sidebar likely reads from a different data source than the one you patched. Ensure all consumers read from the same store, such as a getChatById selector, so local patches propagate to headers, detail views, and lists.