This repository has been archived by the owner on Sep 4, 2023. It is now read-only.
Fix outcomes being capped at 100 #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm going to merge this one into beta enhancements, and also perform the necessary clean up if that's alright. |
|
Yeah go ahead |
|
Thanks for your contributions :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry I don't have time right now to clean it up, but this fixes the outcomes being capped at 100 due to lack of pagination. The 'proper' way to do it is to follow the Link.Next header but also setting
page={it}&offset={it*limit}works so I used the quick & dirty way, and just check if Link.Next is null.