New
Introducing React Bench, see how different models perform on React code
Menu
What Is React Doctor?
Quickstart
Install for Coding Agents
How to Fix Issues
GitHub Actions Setup
Updating CI
Other CI Providers
Migrating to CI v2
Config Files
ESLint & oxlint Plugins
Add Custom Rules
CLI Reference
GitHub Action Reference
Node.js API
Changelog
Modified MIT License
Terms of Service
Privacy Policy
Data Use
Security
Support
Rules reference

react-doctor/query-destructure-result

Destructure the query result instead of binding the whole object: const { data, isLoading } = useQuery(...)

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Fires on a VariableDeclarator whose id is a plain Identifier (not an ObjectPattern/ArrayPattern) and whose init is a CallExpression whose callee is itself an Identifier matching one of the four TANSTACK_QUERY_HOOKS: useQuery, useInfiniteQuery, useSuspenseQuery, useSuspenseInfiniteQuery — i.e. const query = useQuery(...) where the whole result is captured under one name. It does NO scope or usage analysis: it reports unconditionally on that shape regardless of how the binding is later used. Only two real exclusions, both structural: already-destructured (node.id is an ObjectPattern or ArrayPattern, so const { data } = useQuery(...) never matches), and a callee that is not literally one of those four Identifiers (a member-expression call like queryClient.fetchQuery, a wrapper hook of your own, or a same-named local Identifier that is not the TanStack import). False positive is a reviewer judgment, not a detector suppression: the rule still fires when the whole object must legitimately be held as one value (forwarded as-is to a child, returned untouched from a custom hook, or kept to spread later) — suppress those manually.

How to fix

Follow the rule guidance while preserving unrelated behavior.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Replace the whole-object binding with a destructuring pattern naming only the fields this scope reads, e.g. change const query = useQuery(...) to const { data, isLoading, error } = useQuery(...), then rewrite each query.data / query.isLoading reference to the bare field. This keeps TanStack Query's tracked-property optimization working so the component re-renders only when a field it actually reads changes; capturing the whole object and reaching in via property access subscribes to every field. If the result genuinely must be passed around as one object, leave it and suppress. https://tanstack.com/query/latest/docs/framework/react/guides/render-optimizations

More Bugs rules from the rules reference: