Prevent settings drift
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the configuration handling for screenly.yml and mock-data.yml, then read how settings are loaded and compared. The work is done when introducing a setting in screenly.yml that is absent from mock-data.yml reliably raises an actionable error.
Written by the indexing model from the issue text.
Description
So let's say you are working on a local app and introduce a new setting to screenly.yml with mock-data.yml present. It is then very easy to lose a lot of time trying to figure out why the new setting that you just introduced isn't available.
What instead would make a lot of sense is to have a 'drift detection' feature where if you introduce a new setting in screenly.yml that isn't present in mock-data.yml, we would raise an error.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 7
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
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.
More from Screenly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100