Skip to content
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

Add get_next and use it from _paginate_response as well #29

Merged
merged 3 commits into from Feb 19, 2022

Conversation

Disruption
Copy link
Contributor

@Disruption Disruption commented Feb 19, 2022

Changes

This is a QoL update.
This PR adds a public entrypoint "get_next" to fetch the next page of results after an existing response.
This allows client users to paginate manually without having to do all the boilerplate checks and without having to explicitly use the field name for "next" or having to control page size and result size manually (via $top and $skip parameters passed to the request).

@ingmferrer ingmferrer merged commit 4b78664 into GearPlug:master Feb 19, 2022
@Disruption Disruption deleted the feature/get_next_page branch February 19, 2022 17:26
@ggravlingen ggravlingen mentioned this pull request Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants