-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support customizing initialPageParam
#141
Comments
It should have been resolved in v1.6.1. |
Hi Guys I uses 1.6.1, if i don't set initialPageParam in cli, It sends query page param as "initialPageParam" rather then default value 1 api/customers?page=initialPageParam&limit=10&search= If it works like this please update the README Thanks. |
This issue is expected to be resolved in #149. |
Is your feature request related to a problem? Please describe.
The newly added Infinite Query support generates a hard-coded
initialPageParam: 1
. This prevents use with cursor-based or zero-indexed pagination APIs.Describe the solution you'd like
Support customizing the
initialPageParam
, be it null, string, or number.Describe alternatives you've considered
I'll have to manually define the infinite query in the meantime, utilizing the generated API client.
The text was updated successfully, but these errors were encountered: