cleodora-forecasting / cleodora-forecasting/cleodora
[Idea] Allow users to store frontend preferences in the DB
Open
- Dominant language
- Go
- Stars
- 24
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Could be things such as:
* Stop displaying version reminders #583
* Language
* Default view to display
* Default resolution time
All these things could be stored in cookies but that has the disadvantage that they would be gone when switching browsers. For that reason it's better to keep these things in a separate DB table.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing issue #583 and the current cookie-based handling of version reminders, language, default view, and resolution time. Done would require an agreed design for storing these preferences in a separate database table and using them across browsers.
Written by the indexing model from the issue text.
Assessment
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100