You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Current useInfiniteQuery is great, however in some cases the response won't conveniently contain a nextPageParam parameter. Notable example being Spring Page responses, which serializes to something like the following:
I tried but found no way to customize the springdoc behavior to generate something like a nextPage in this format.
Describe the solution you'd like
Have a CLI option to generate useInfiniteQuery which accepts a getNextPageParam callback that I can implement in the frontend.
Describe alternatives you've considered
Cannot think of any at the moment.
Additional context
There is also a PagedModel in Spring, however this does not contain a next page number field either. It contains a nextLink instead.
My current use case more pertains to the Page response.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Current
useInfiniteQuery
is great, however in some cases the response won't conveniently contain anextPageParam
parameter. Notable example being SpringPage
responses, which serializes to something like the following:I tried but found no way to customize the springdoc behavior to generate something like a
nextPage
in this format.Describe the solution you'd like
Have a CLI option to generate
useInfiniteQuery
which accepts agetNextPageParam
callback that I can implement in the frontend.Describe alternatives you've considered
Cannot think of any at the moment.
Additional context
There is also a
PagedModel
in Spring, however this does not contain a next page number field either. It contains anextLink
instead.My current use case more pertains to the
Page
response.The text was updated successfully, but these errors were encountered: