feat: Add limit to Client keys pagination #99563
Merged
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
github-actions
bot
added
the
Scope: Backend
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #99563 +/- ##
=======================================
Coverage 81.24% 81.24%
=======================================
Files 8588 8588
Lines 380057 380057
Branches 24074 24074
=======================================
+ Hits 308771 308773 +2
+ Misses 70923 70921 -2
Partials 363 363 |
vgrozdanic
approved these changes
Sep 16, 2025
priscilawebdev
deleted the
priscila/feat/client-keys/add-limit-to-pagination
branch
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.
When users have many client keys, the page loads a long list and the scroll becomes too lengthy. I think showing 10 per page would be a good balance