How to handle paginated endpoints with no Link header #605
Closed
bennettscience
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
It's been a while since I've looked at the It might be possible to first try to get the info from |
Beta Was this translation helpful? Give feedback.
1 reply
-
Looks to be resolved in #614 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on #565 right now and have run into an issue with paginating the responses.
LiveAssessments are a tool in Canvas to give feedback on Learning Outcomes in your course. The Magic Marker app used to use this, but Instructure hasn't done anything with it in ages. The problem is in how the endpoint returns paginated responses.
Instead of using a
Link
header that thePaginatedList
class can use, the links to paginated responses are in the body of the response. This happens for anylive_assessment
endpoint, including for results.There are a couple ways I could handle this:
LiveAssessment
class an iterable on its own. The user could use it just the same as thePaginatedList
responses.list
of live assessments or results, but not make the class itself iterable.Does one of these stand out as better or worse than another? Given how little it's actually used in Canvas, I don't have a strong opinion one way or another.
Beta Was this translation helpful? Give feedback.
All reactions