-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pagination for GET requests #69
Comments
The
This would be my recommendation as well. |
While |
Personally, I am -1 to An absolutely unscientific survey: reddit does this by |
@mathuin Are you sure that's how reddit does it? Maybe internally or something. I've only ever seen my address bar show Edit: Nope, I see now. New discovery. Reddit, which has true pagination, uses |
My 'next' button at the bottom of my Reddit home page currently has this link: |
@mathuin So even Reddit and its users can't agree on it, it seems. |
Also see this issue
It would be a very useful feature to be able to paginate GET requests (especially requests to the
/times
endpoint). In the previously mentioned issue, @LyonesGamer suggested that?limit
and?skip
parameters be added (to correspond to LIMIT and OFFSET queries on an SQL database). The behavior for these parameters might look something like this:?limit=:numobjects
?skip
isn't specified, it defaults to 0?skip=:toskip
?limit
isn't specified, it defaults to all objects after :toskip objectsFor ordering the objects for either of these parameters, it could be specified that the objects should be returned in order of creation date with the most recently created object first.
The text was updated successfully, but these errors were encountered: