Pagination in Admin Api V2 #41036
shawkins
started this conversation in
API guidelines
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
@sschu just wanted capture some of what I was trying to convey in the meeting and some points that were mentioned in earlier design docs. Please add what you have, and I'll add some more about using a continuation token.
Additional Considerations:
For all resources which will not have an excessive number of entries (possibly everything except for users) we don't need to offer sort and slice features. Instead admin api clients via projection would obtain the indentifier fields and any sorting columns, perform their own client-side sort, then fetch whatever pages they want by identifier. We could add support for bulk fetching by id to cut down on the number of api queries.
For resources with an excessive number of entries, or for which we do want to offer sorting / slicing:
Skipping pages isn't strictly necessary, but is a nice to have feature.
cc @mabartos @vmuzikar
Beta Was this translation helpful? Give feedback.
All reactions