state/query-key-deps

Dlaczego

The key is the cache address and the only thing TanStack Query watches. With queryKey: ['todo'] and queryFn: () => getTodo(id), every todo shares one cache entry: open todo 2 after todo 1 and the page shows todo 1's data, and changing id never refetches.

Poprawka

Put every value the query function uses into the key, in order from general to specific: queryKey: ['todo', id], ['todos', { status, page }]. In Vue pass the ref or getter itself (['todo', id]), not id.value. Build keys and functions together with queryOptions() or a key factory so they cannot drift apart, and enable @tanstack/query/exhaustive-deps in ESLint.

Przykłady

// bad
useQuery({ queryKey: ['todo'], queryFn: () => getTodo(todoId) })
// good
useQuery({ queryKey: ['todo', todoId], queryFn: () => getTodo(todoId) })

Źródła

• TanStack Query docs, Query Keys (if your query function depends on a variable, include it in your query key)
• TanStack Query docs, ESLint rule exhaustive-deps

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain state/query-key-deps