-
Notifications
You must be signed in to change notification settings - Fork 0
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 in Queries #48
Comments
I think this is missing one more case that Koype handles, if there's no more preceding items in the list, there should be no expectation of a (Originally published at: https://jacky.wtf/2022/7/_TEm) |
@jalcine I think that's exactly what Microsub describes as how to poll for new content |
Noted! (Originally published at: https://jacky.wtf/2022/7/QXZe) |
This covers the concept of adding pagination to queries. This would be an alternative to the simpler offset #36 parameter.
Pagination was originally noted in #4 as part of multiple suggestions and is based on the Microsub spec https://indieweb.org/Microsub-spec#Paging for paging. A summary adapted from there is noted below.
For queries that paginate their results, there is an additional object returned with the values needed to page through those results.
"paging": {
"before": "xxxxx",
"after": "xxxxx"
}
The "before" and "after" values are arbitrary strings. This allows the server to internally use whatever specific implementation is most appropriate for its backend technology. (Often this will be either a timestamp or a unique ID identifying the first and last items in the returned list.)
The text was updated successfully, but these errors were encountered: