-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use paginate function with custom option parameters #797
Comments
ghost
changed the title
How to use paginate function with other option parameters
How to use paginate function with custom option parameters
Oct 25, 2022
I see what you're trying to do. The links should really be added to the transform meta method so you can customise the links. For now you can do this manually but I'll look at add this in as a feature |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want to be able to use function paginate, but being able to remain my current filters query params.
For instance, I have the following endpoint:
As you can see, I have added the option type over there...
But I cannot see this reflected on the links object when browsing in the api.
I would like to see it for example when applying the query params of type=fire:
"next": "http://localhost:3000/pokemons?page=2&limit=10&type=fire",
What am I doing wrong here?
The text was updated successfully, but these errors were encountered: