This repository was archived by the owner on Jul 8, 2025. It is now read-only.
fix: implement server side pagination in frontend #368
Conversation
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
alex-mcgovern
changed the title
Pull Request Test Coverage Report for Build 13786985073Details
💛 - Coveralls |
…gate-ui into fix/server-side-pagination
…n page number is > 1
peppescg
approved these changes
Mar 11, 2025
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.
Handles the API changes from:
Relates to stacklok/codegate#1020
Something important to call out is the backend doesn't support search/filtering by substring — I'm tracking this separately: [Task]: Investigate feasability of filtering workspace messages by substring in prompt
There is also some extra testing that can be done around the pagination UX, also tracked separately: [Task]: Follow up integration tests for messages pagination