Siderite / Siderite/lichessTools
Create a user scoped mechanism for settings saved locally, maybe even Preferences
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 92
- Forks
- 20
- Avg merge
- 19h 59m
- Merged PRs (30d)
- 1
Description
When you change something, it has to be saved under and .username. When reading the value, read it from the user scope and if not found, from the general scope.
But this might introduce a lot of weird behavior. What if you sign out and then change a value? When you go minimal or restore some values, what do you do?
Needs careful attention.
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.
Research direction
Start by tracing how the extension currently saves and reads local settings, then inspect the sign-out, minimal, and restore flows mentioned in the issue. Document the intended behavior for user-scoped values, fallback to general values, sign-out changes, and restore operations before implementing and testing the mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100