Skip to content

Implement stored user preferences. #16

Closed
campb303 opened this issue Aug 6, 2020 · 4 comments
Closed

Implement stored user preferences. #16

campb303 opened this issue Aug 6, 2020 · 4 comments
Labels
feature-request Request for functionality that has not already been implemented

Comments

@campb303
Copy link
Collaborator

campb303 commented Aug 6, 2020

After #15 is completed, there should be a mechanism for storing and syncing user based preferences across devices for settings such as dark mode and saved searches.

@campb303 campb303 added the feature-request Request for functionality that has not already been implemented label Aug 7, 2020
@campb303 campb303 added this to the v1 milestone Sep 14, 2020
@campb303 campb303 modified the milestones: v1, v2 Sep 22, 2020
@campb303 campb303 modified the milestones: v3-write-access, v2-production-ready-read-only Feb 5, 2021
@campb303
Copy link
Collaborator Author

campb303 commented Feb 5, 2021

Several discussions have come to the need for syncing user preferences in a central location. The settings include:

  • Dark mode setting
  • Saved searches
  • ItemTable column visibility
  • ItemTable column reordering

@campb303
Copy link
Collaborator Author

Without a proper database, this can be implemented client side for a per device config.

@campb303
Copy link
Collaborator Author

Implementing a client side setting store would eventually need to be reworked to use a server side database solution and change how the application works. Instead, we can use SQLite server side and make queries via a database management tool that abstracts specific database engine workings like SQLAlchemy. Later we can simply switch the database backend while keeping the logic for the API and frontend the same.

@campb303
Copy link
Collaborator Author

API portion of this moved to ECN/webqueue2-api#9

Frontend item can be remade when API item is completed.

Sign in to join this conversation on GitHub.
Labels
feature-request Request for functionality that has not already been implemented
Projects
None yet
Development

No branches or pull requests

1 participant