Skip to content

feat(client): Changes view with Only edits and In repo maps - #410

Merged
byronwall merged 3 commits into
change-lens/panelfrom
change-lens/map
Nov 22, 2026
Merged

byronwall merged 3 commits into
change-lens/panelfrom
change-lens/map

Conversation

@byronwall

@byronwall byronwall commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

A fourth view, Changes, beside Treemap, Graph and 2×2. It draws only the chunks a window edited, or the whole file map with untouched files muted. In this layer it runs on mock data (?view=changes&clmock=1); #411 joins it to the real API. Part of #397.

What you'll see

  • Changes in the view switch, with window presets (This branch, 24 hours, 7 days, Custom), Touched / Net, and Only edits / In repo.
  • Only edits packs the edited chunks by folder and file. Tile area is changed lines.
  • In repo shows the file map by LOC. Untouched files are muted and each edited chunk is a band in its file.
  • Color by a metric now, or by its change. Added, deleted, moved, reverted and not-measured chunks each have their own look.
  • The selection, layout, lens and window are in the URL, so Back and refresh restore them.
  • Without clmock=1, the view shows an error state until the top layer lands, because this layer's request shape is not yet joined to the server.

Proof

Only edits, colored by complexity delta, mock data
Only edits on the mock payload: chunks grouped by folder and file, with before → after on each tile and one chunk selected.

In repo, zoomed to one folder, mock data
In repo: untouched files muted, edited chunks drawn as bands, the same chunk still selected.

  • The map worker's browser pass on the mock: a color change moved 0 tiles and kept the selection; a layout switch kept the selection; Back and refresh restored the state; Net showed 0 reverted tiles.
  • 15 vitest tests cover packing with the area floor, folder labels, URL state and tile states. On the top of the stack, scripts/check.sh client passes with 492 tests.
  • These screenshots use mock data and stand-in panel components. The real ones are in feat: Change Lens on real history, with docs #411.

Limits

  • Not verified against the real API in this layer.
  • Collapsed groups are not in the URL.

Stack: Change Lens, layer 3 of 4

This slice: The Changes view: window bar, both maps, lenses, legend and URL state.
Why it is its own layer: It edits three shared client files (location.ts, TreemapHeader.tsx, Treemap.tsx) and is the largest client diff. Keeping it apart from the join keeps the fixes in #411 readable.
Full story: #408

Survey moves: +5 partial traces in client and their stops (frontier: disconnected +36, frontier: budget-exhausted +17, frontier: unresolved-symbol +3, boundary: unproven-handoff +2, boundary: network +1, frontier: external-code -1). All come from the new client/src/changelens/ view files entering the surveyed corpus. No analysis code changed and no trace errored.

🤖 Generated with Claude Code

@byronwall
byronwall added this pull request to stack #412 November 21, 2026 23:58
@byronwall byronwall changed the title change lens/map feat(client): Changes view with Only edits and In repo maps Nov 21, 2026
byronwall and others added 3 commits November 21, 2026 22:00
…#397)

The fourth view, ?view=changes. A window bar picks the window, touched or
net, the map and the color lens. Only edits packs the edited chunks by
folder and file, with area by changed lines and a floor. Show in repo
marks the chunks on the file map. The panel and the commit rail are
stand-ins in slots.tsx. ?clmock=1 answers from sample.ts until the server
has /api/change-lens.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@byronwall
byronwall marked this pull request as ready for review November 22, 2026 03:03
@byronwall
byronwall merged commit 4ab3d69 into main Nov 22, 2026
12 of 13 checks passed
@byronwall
byronwall deleted the change-lens/map branch November 22, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant