Open JoshPiper opened 2 years ago
What would your use case for this be?
What would your use case for this be?
As an example, going through addon versions, to get the total number of pages required, the cursor would need to be fully expended before a final count could be given.
So any paged pagination, as opposed to infinite scroll pagination, essentially.
Feature
Having a total or count field for listX requests in the v3 API would help for purposes of pagination. The current cursor based pagination works well for infinite scrolling, but requires that every page of data is requested before a total can be given, even if only one page is required.
Additional Information
No response