fix(ui): persist filters and sorting in several admin stores #5253
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.
Description:
This PR introduces improvements to how filters and sorting are managed for the Devices, Users and Namespace sections in the admin UI. Specifically:
State Persistence:
Moved filter, sortField, and sortOrder state into their respective stores (devices, users and namespace) using reactive variables.
Refactored Fetch Logic:
Updated fetchDeviceList, fetchNamespaces and fetchUsersList to default to the store's current filter/sort values if none are explicitly passed.
Minor Cleanups:
Testing: