We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Support pulling next URL from response body, such as for HATEOAS APIs.
HATEOAS response might look like:
{ "_links": { "self": { "href": "/orders" }, "next": { "href": "/orders?page=2" }, "find": { "href": "/orders{?id}", "templated": true } }, "currentlyProcessing": 14, "shippedToday": 20 }
fetchPaginate('https://api.example.com', { getNextUrl: ({ body }) => body?._links?.next?.href })
or possibly support a string path (nicer for CLI):
fetchPaginate('https://api.example.com', { getNextUrl: '_links.next.href' })
Not sure how (or whether) to handle templated links.
The text was updated successfully, but these errors were encountered:
Can this be done today with the next option? Not sure - should check.
next
Sorry, something went wrong.
AndersDJohnson
No branches or pull requests
Support pulling next URL from response body, such as for HATEOAS APIs.
HATEOAS response might look like:
or possibly support a string path (nicer for CLI):
Not sure how (or whether) to handle templated links.
The text was updated successfully, but these errors were encountered: