usefulsoftwareco Effect-atom write mutations must say which reads they invalidate.
Fix Shape
- Find the
useAtomSet(...)write mutation call. - Add
reactivityKeysto the mutation payload at the call site. - Use the narrowest keys that cover the rows/lists affected by the write.
- Keep read-only probe/preview OAuth flows out of this pattern.
- If the mutation should update UI immediately, check whether
wrdn-effect-atom-optimisticalso applies.
Good
await updateSource({
params: { scopeId, sourceId },
payload,
reactivityKeys: [["sources", scopeId]],
});