Skip to content

feat(ui): plan page in tabs, folder lineage and readable job graphs - #1442

Merged
kvlonge merged 4 commits into
mainfrom
feat/ui-plan-lineage
Nov 13, 2026
Merged

kvlonge merged 4 commits into
mainfrom
feat/ui-plan-lineage

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Why

The plan page still had a permissions side panel and a plain list, and large projects drew unreadable graphs: lineage above a few hundred nodes became a cramped column, and a job or group whose nodes share a rank (marts with little lineage inside the job, staging models off one source) drew as one column hundreds of cards tall.

Changes

  • Plan page: no side panel; options show as chips in the summary. A one-sentence summary says what the run does (what changed, what builds for the first time, what takes new rows, what is recreated as usual, and seeds, functions, Python nodes and disabled models). The graph has its own tab, and a Checks tab lists the checks that run after the planned models and seeds, with their last outcome.
  • Lineage: above 150 nodes the graph opens as folder cards (models by path folder, sources by file, a declared group first) that open into nested folders and then nodes. A Folders toggle switches back. The inspector's upstream and downstream lists and SQL links reach nodes inside closed folders.
  • Job and group graphs: each box is laid out on its own, then boxes and loose cards together, so a box always sits right of the boxes it runs after. A column taller than the canvas suits wraps into several, stacked side by side. Graphs that need no wrapping keep their layout; a group whose lineage loops between boxes keeps the single layout, so no edge runs backwards.

Verification

  • uv sync --all-extras && make check-ci passed on this head.
  • ui: npm run check (0 errors), npm test (216 passed), npm run build.
  • New tests cover column wrapping, unchanged small layouts, after boxes staying right of their upstream box, lineage looping between boxes, and the plan sentence for seed-only, function-only and disabled cases.
  • Checked rendered pages on a local sqb server with a DuckDB DuckShop location: the plan page tabs, lineage folders at 334 nodes, and job graphs at 69, 99 and 168 nodes, plus the mock data's small graphs.

The plan takes the full width. Permission problems already show next to
the Run button, so the Permissions panel only repeated them, and the
command's options now show beside the plan's summary.
@kvlonge
kvlonge enabled auto-merge November 13, 2026 08:20
@kvlonge kvlonge added the full-verify Run the full Verify matrix on this pull request label Nov 13, 2026 — with Amp for GitHub
@kvlonge
kvlonge added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit f242cb2 Nov 13, 2026
55 checks passed
@kvlonge
kvlonge deleted the feat/ui-plan-lineage branch November 13, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-verify Run the full Verify matrix on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant