Web UI: config editor — baseline diff view + session snapshot history

Open
#154 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement frontend

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from falbany/ProFiles

All issues in falbany/ProFiles

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.