You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the non-alpha release I'm going to support forwards pagination only - after: and endCursor and hasNextPage. I can support startCursor too at this point even though it's not useful for anything yet.
I'll split hasPreviousPage and before: into a separate ticket. Originally posted by @simonw in #2 (comment)
The text was updated successfully, but these errors were encountered:
This may be blocked by Datasette core support for reverse pagination: simonw/datasette#916 - but I can go ahead and implement this independently and use that implementation to inform a later change to Datasette.
You may order the edges however your business logic dictates, and may determine the ordering based upon additional arguments not covered by this specification. But the ordering must be consistent from page to page, and importantly, The ordering of edges should be the same when using first/after as when using last/before, all other arguments being equal. It should not be reversed when using last/before. More formally:
When before: cursor is used, the edge closest to cursor must come last in the result edges.
When after: cursor is used, the edge closest to cursor must come first in the result edges.
simonw
changed the title
Reverse pagination: hasPreviousPage and before:
Reverse pagination: hasPreviousPage and before: and last:
Aug 8, 2020
For the non-alpha release I'm going to support forwards pagination only -
after:
andendCursor
andhasNextPage
. I can supportstartCursor
too at this point even though it's not useful for anything yet.The text was updated successfully, but these errors were encountered: