Repository navigation
feat(ui): plan page in tabs, folder lineage and readable job graphs - #1442
Merged
Merged
Conversation
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
enabled auto-merge
November 13, 2026 08:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Verification
uv sync --all-extras && make check-cipassed on this head.ui:npm run check(0 errors),npm test(216 passed),npm run build.afterboxes staying right of their upstream box, lineage looping between boxes, and the plan sentence for seed-only, function-only and disabled cases.sqb serverwith 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.