feat(admin): paginate audit trail (web/admin 0.1.17)#6
Merged
Conversation
Add client-side pagination (25/page) to the Audit tab via Cloudscape Pagination over the existing capped fetch; page resets to 1 on refresh. Bump admin image tag in k3s + example overlays.
|
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
1 participant
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.
What
Adds client-side pagination to the Audit trail tab in the admin web UI.
Paginationcontrol, wired into theTable'spaginationslot.limit=1000in one request) — no backend change, instant page switches.Version / deploy
admin/web/package.json: 0.1.16 → 0.1.17platform/overlays/k3sandplatform/overlays/example.After merge: trigger
image-admin.yml(gh workflow run image-admin.yml -f tag=0.1.17) to build & push the image, thenkubectl apply -k platform/overlays/k3sto roll out.Notes
Pagination is client-side over a capped fetch. If the audit table ever grows past ~1000 rows, we'd want true server-side paging (the API already accepts a
limit; would addoffset/cursor).