feat: add user preferences persistence (theme, scoop interval, table …#616
Open
noor1ha wants to merge 1 commit into
Open
feat: add user preferences persistence (theme, scoop interval, table …#616noor1ha wants to merge 1 commit into
noor1ha wants to merge 1 commit into
Conversation
…columns) Add frontend infrastructure for saving user preferences across sessions. Preferences are stored locally in Redux and synced to the backend via REST endpoints (GET/PUT/DELETE /api/v1/preferences).
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
2 participants
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.
kube-HPC/hkube#2364
Title: User Preferences Persistence — Frontend Implementation
What: Allows users to save UI preferences (theme, scoop interval, table column visibility/widths) to the backend so they persist across sessions and devices.
How it works:
Backend dependency: Requires 3 new API server endpoints (GET/PUT/DELETE /api/v1/preferences) backed by a MongoDB userPreferences collection. Frontend works without them (graceful fallback to defaults).
This change is