​

Mutation Standardization

​

Objective

​

Rules

• all writes belong in hooks/mutations/
• no page or component should perform app-data writes with raw fetch
• every write should be wrapped by useMutation
• prefer onSuccess plus invalidateQueries
• do not use setQueryData or setQueriesData for this migration

​

Standard Pattern

export function useUpdateAccountType() {
  const queryClient = useQueryClient()
  const { user } = useUser()
  const userId = user?.id ?? ''

  return useMutation({
    mutationFn: updateAccountType,
    onSuccess: async () => {
      await queryClient.invalidateQueries({
        queryKey: userKeys(userId).accounts.all,
      })
    },
  })
}

​

Why We Are Avoiding setQueryData

• invalidation is easier to reason about across many domains
• invalidation is easier to audit in code review
• invalidation reduces drift between server truth and local cache assumptions

​

Required Refactors

​

Move writes out of components/pages

• hooks/mutations/use-update-account-type.ts
• hooks/mutations/use-update-account-tax-treatment.ts
• hooks/mutations/use-disconnect-account.ts
• hooks/mutations/use-process-snaptrade-connection.ts

​

Update call sites

const updateAccountType = useUpdateAccountType()

await updateAccountType.mutateAsync(payload)

​

Replace local cache writes

​

Review Checklist

• is the write implemented in hooks/mutations/?
• does the hook own the fetch call?
• does onSuccess invalidate the narrowest correct key family?
• did we remove any direct page/component fetch write logic?
• did we eliminate setQueryData or setQueriesData from the touched path?