Allow pageParam to be a string within generated infiniteQueries #146

Activity

1. 7nohe

   added

   enhancementNew feature or requestNew feature or request

   on Sep 16, 2024
2. 7nohe

   self-assigned this

   on Sep 16, 2024
3. 7nohe

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

   feat: make initialPageParam and getNextPageParam overridable in infin…

   ...

   a85f3b1
4. 7nohe commented on Aug 11, 2026

   

   7nohe

   on Aug 11, 2026

   Owner

   More actions

   Fixed in v3.0.0.

   The generator now resolves the page parameter's type from the schema — including through type aliases — and emits a matching type in all three positions instead of hardcoding number. For a spec where the cursor is Cursor: { type: string }:

   queryFn: ({ pageParam, signal }) => listItems({ ...clientOptions, query: { ...clientOptions.query, page: pageParam as Cursor }, ... })
   initialPageParam: "1",
   getNextPageParam: (response: unknown) => (response as { nextPage: Cursor }).nextPage,

   No as number on the string path, and initialPageParam is quoted so it stays a string.

   Two things worth knowing for a cursor-based API, since a default of "1" is rarely meaningful as a cursor:

   • --initialPageParam "" emits initialPageParam: ""
   • --omitInitialPageParam (added in v3) omits the page parameter from the first request entirely, which is usually what a cursor API wants — the server returns the first page when no cursor is supplied

   Available on latest (npm i @7nohe/openapi-react-query-codegen@3). Thanks for the report, and sorry it took a while.
5. 7nohe

   closed this as completedon Aug 11, 2026