Web UI: config editor — baseline diff view + session snapshot history
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Read ConfigEditorModal.tsx around the baseline hash at lines 359–364 and markSaved around lines 723–766, then inspect the existing Revert and pendingAction flow. The issue also points to utils/ for a pure LCS diff utility and references #116, #105, #111, and #147 for related behavior. Done means the editor can show baseline-to-draft changes and list and restore session save snapshots through the existing confirmation flow.
Written by the indexing model from the issue text.
Description
Idea
Two editor features that build directly on the #116 staleness machinery:
1. Baseline diff view. The editor already loads the baseline text and hashes it for the staleness guard (ConfigEditorModal.tsx:359-364), but only the hash is kept. Keep the baseline text in a ref next to baselineHashRef and add a "Diff" toggle that renders a line-level diff (small pure LCS util in utils/) between baseline and draft before Apply/Save — users see exactly what will be written, complementing the Problems panel from #105/#111.
2. Session snapshot history. The editor tracks a save baseline per save (markSaved, lines 723-766). Add a "History" entry to the header listing the session's saved snapshots (text + timestamp kept in a ref stack); restoring one reuses the existing Revert/pendingAction confirm flow and the swap-doc path (which #147 will have made undo-friendly). Purely client-side — no server change needed for session history. (Disk-side history would be a separate, larger feature.)
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 55
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 falbany/ProFiles
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
falbany/ProFiles#187 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in falbany/ProFiles
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ip-tools/patzilla#219 · 2 comments ·
Maintainers usually reply within 1 day
-
EPSSClient commits to its SQLite cache once per score: a 100-CVE bulk fetch makes 101 disk flushesOpenpriority:p3 technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jimmy058910/jmo-security-repo#1673 ·
Maintainers usually reply within 1 day
-
enhancement ready
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
integration: frontier_silicon
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
home-assistant/core#193176 · 2 comments ·
Maintainers usually reply within 1 day
-
task create and task update take --body-file and --stdinPossibly taken @JuanBarriosS claimed this today. Opencli enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyrite-wiki/pyrite#1687 · 1 comment ·
Maintainers usually reply within 1 day