feat: preserve sort/filter state across view refreshes#477
Open
Ppito wants to merge 1 commit into
Open
Conversation
0e19e28 to
14ff532
Compare
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.
Problem
When the auto-refresh triggers a view reload, the current sort order or/and active filters are lost. This forces the user to reapply them manually after each refresh cycle, which degrades the experience significantly when monitoring data over time.
Solution
Introduce an in-memory state that holds the active sort and filter parameters for the duration of the session. This state is initialized once and passed through (or stored at a scope that survives) the refresh loop, so each reload restores the view with the same sort/filter configuration the user had set.
Changes