UI: Add saved views to persist table filters and sorting#68484
Draft
pierrejeambrun wants to merge 1 commit into
Draft
UI: Add saved views to persist table filters and sorting#68484pierrejeambrun wants to merge 1 commit into
pierrejeambrun wants to merge 1 commit into
Conversation
pierrejeambrun
requested review from
bbovenzi,
choo121600,
guan404ming,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
boring-cyborg
Bot
added
area:translations
area:UI
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.
Adds saved views to the data tables: once you've applied filters / search / sorting to a table, you can save that state under a name and restore it later from a dropdown above the table, or delete saved views you no longer need.
A "view" is the table's current URL query string (filters, search, page size) with the active sort baked in (sort is mirrored to
localStorageand is often absent from the URL, so it's captured explicitly); pagination position is dropped so a restored view starts on page one. Views are stored per-page inlocalStorage(per browser), mirroring how table sort/limit are already persisted. The control lives in the sharedFilterBar, so every filterable table gets it automatically.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines