Pagination Part 2 - #308
Merged
Merged
Conversation
willchen96
marked this pull request as ready for review
August 12, 2026 09:43
willchen96
approved these changes
Aug 12, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This implements pagination across the remaining main list views.
Why / Motivation
This lets the UI support larger datasets through loading parts of the data set as needed for the view.
Changes
The pagination pattern approved in the first branch has been implemented across the other views. The exception is the file view which loads folder child content when clicked, rather than using a batching call with scroll.
Tradeoffs & risks
Similar considerations to the previous design pass for the initial pagination implementation. Re: files - if there are large sets of files in the root or in a single folder, the current solution will be sub-optimal, as it fetches these in a single hit.
How verified
Verified with local smoke testing on the ui using seed data generated with sql scripts.
Checklist
git diffand removed unrelated changes..envfiles committed.