Persist DiffsHub display preferences
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reviewing linked pull request #853 and the existing DiffsHub display controls. Check how their current defaults and preference state are handled. Done means the listed display preferences persist locally with versioning and schema validation, while users without stored settings retain current defaults; account-backed settings and per-URL review/comment state are out of scope.
Written by the indexing model from the issue text.
Description
Problem
DiffsHub display controls currently reset between visits. This makes repeated review sessions more frictionful because users need to reselect their preferred split/unified view, wrapping, line numbers, backgrounds, and indicator style.
Proposed scope
Persist display preferences locally in the browser:
- split/unified diff style
- word wrap / horizontal scroll
- line number visibility
- background visibility
- diff indicator style
The persistence should be client-only, versioned, schema-validated, and preserve current defaults for users without stored settings.
Non-goals
- Account-backed settings
- Server persistence
- Changing current default display behavior
- Persisting per-URL review/comment state
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 226
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 40
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 pierrecomputer/pierre
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pierrecomputer/pierre#1187 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pierrecomputer/pierre#1150 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
pierrecomputer/pierre#1229 ·
Maintainers usually reply within 1 day
-
[highlights] 146 Shiki languages have no lexer (prisma, ini, dotenv, ansi, ...)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 38/100
pierrecomputer/pierre#1228 · 1 comment ·
Maintainers usually reply within 1 day
-
KDL language supportOpen
Difficulty 3/5 1-2 days Newbie friendliness 59/100
pierrecomputer/pierre#1222 ·
Maintainers usually reply within 1 day
All issues in pierrecomputer/pierre
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grafana/profiles-drilldown#1212 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
grafana/traces-drilldown#980 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openremote/openremote#3487 · 1 comment ·
-
triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
garrytan/gbrain#7635 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
coollabsio/jean#867 ·
Maintainers usually reply within 1 day