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
Describe the bug
Requests that return multiple items will be paginated to 10 items by default. To retrieve more items, you can either append a ?per_page parameter or utilise the Link header to check if the next page exists and if it does, get the next page of items.
Currently, this wasn't taken into account and at max, 10 items are returned for requests that might actually return more than 10 items (for example files in a folder).
Possible to look into a recursive kind of check for existence of next page for Canvas APIs?
Idea: After building a Request, Send() will not just retrieve the response for that request, but also check if there are additional pages for that response via the response header. If there is, append to the original response. Repeat until the last page.
Describe the bug
Requests that return multiple items will be paginated to 10 items by default. To retrieve more items, you can either append a
?per_page
parameter or utilise theLink
header to check if the next page exists and if it does, get the next page of items.Currently, this wasn't taken into account and at max, 10 items are returned for requests that might actually return more than 10 items (for example files in a folder).
For ref: https://canvas.instructure.com/doc/api/file.pagination.html
The text was updated successfully, but these errors were encountered: