LizardByte / LizardByte/roadmap
Sunshine: improve config backend
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Description
### Is there an existing issue for this item?
- [x] I have searched the existing issues
### Repositories
LizardByte/Sunshine
### Languages/Skills/Technologies
C++, Vue, HTML, CSS, JavaScript
### Description
Instead of hardconding the config options in the Frontend, the Backend returns a list of configuration options and the possible values, so that the Backend can dynamically populate the settings and make the frontend less convoluted - we wouldn't be able to make this for all options, but at least many simple configuration switches could be added without touching the Frontend
### Estimated Effort
effort:Large
### Priority
priority:Medium
### Target Milestone
6+ months
### Dependencies
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how configuration options are defined in the Backend and how the settings are populated in the Frontend. Define which simple switches can be returned with their possible values, then verify that the selected options are rendered and remain configurable without adding frontend-specific definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, css, html, javascript
- Domain
- api, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100