Generates incorrect queryKeys for Infinite queries #140

Activity

1. AnderssonPeter

   changed the title [-]generates incorrect queryKeys for Infinite queries[/-] [+]Generates incorrect queryKeys for Infinite queries[/+] on Aug 19, 2024
2. hanahem commented on Aug 20, 2024

   

   hanahem

   on Aug 20, 2024

   More actions

   Oh thanks for raising this one, I think it causes the issue I raised here:
   #139
3. 7nohe

   added

   bugSomething isn't workingSomething isn't working

   on Sep 16, 2024
4. 7nohe

   self-assigned this

   on Sep 16, 2024
5. 7nohe

   added a commit that references this issue on Jul 10, 2026

   feat: generate queryOptions/infiniteQueryOptions factories and dedica…

   ...

   8486a9f
6. 7nohe

   added a commit that references this issue on Jul 18, 2026

   feat!: hierarchical infinite query keys for granular invalidation

   ...

   e2163b2
7. 7nohe commented on Aug 11, 2026

   

   7nohe

   on Aug 11, 2026

   Owner

   More actions

   Fixed in v3.0.0.

   Infinite queries now get their own key constant and key function, separate from the plain query ones, and the page parameter is excluded from the infinite key at the type level:

   export type FindPaginatedPetsInfiniteClientOptions = Omit<Options<FindPaginatedPetsData, true>, "query"> & { query?: Omit<NonNullable<FindPaginatedPetsData["query"]>, "page"> };
   
   export const useFindPaginatedPetsInfiniteKey = [useFindPaginatedPetsKey, "infinite"] as const;
   export const UseFindPaginatedPetsInfiniteKeyFn = (clientOptions: FindPaginatedPetsInfiniteClientOptions = {}, queryKey?: Array<unknown>) => [...useFindPaginatedPetsInfiniteKey, ...(queryKey ?? [clientOptions])];

   The page value is threaded into the request only (query: { ...clientOptions.query, page: pageParam }), never into the key — so the key stays stable across pages, which is the behaviour TanStack Query expects.

   Note the infinite key nests the plain key as its first segment. That means invalidateQueries({ queryKey: [useFindPaginatedPetsKey] }) still matches both caches, while the "infinite" segment keeps cached InfiniteData from colliding with plain query data.

   A custom page-param name (--pageParam) is respected in the Omit. Available on latest (npm i @7nohe/openapi-react-query-codegen@3). Thanks for the clear report — the two-key-set design is exactly what you proposed.
8. 7nohe

   closed this as completedon Aug 11, 2026