Temporary workaround: use a large pageSize when fetching performance artifacts without pagination #2092
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.
Description
We need to add proper cursor-based pagination ("load more" button) when fetching performance artifacts. As a temporary workaround, this PR adds an arbitrarily large number so we will fetch all artifacts if there are more than 20 (but less than 100,000).
How Has This Been Tested?
Make sure params are sent to the API correctly. The pageSize param was already implemented but not unused.
Merge criteria:
DCOcheck)ok-to-testhas been added to the PR.If you have UI changes