Skip to content

feat(dag-viewer): stack the stage lanes top to bottom - #638

Draft
zzylol wants to merge 1 commit into
stack/cleanup-11-docsfrom
stack/viewer-vertical-lanes
Draft

zzylol wants to merge 1 commit into
stack/cleanup-11-docsfrom
stack/viewer-vertical-lanes

Conversation

@zzylol

@zzylol zzylol commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Stack: #574 → #620 → #618 → #621 → #627 → #625 → #628 → #632 → #634 → #616 → #617 → #622 → #624 → #629 → #630 → #631 → #633 → #635 → #636 → #637 → #638 → #640 → #641

Problem

The Stages view put Stage 0, 1 and 2 side by side, so each lane got about a third of the page. Larger DAGs were squeezed small.

Changes

  • The three lanes are stacked top to bottom: Stage 0 first, the chosen Stage 1 candidate below it, then the chosen Stage 2 candidate. Each lane is as wide as the page allows.
  • The page's maximum width goes from 1,680 px to 1,920 px, and each lane is 560 px tall.
  • The Stage 3 list stays beside the lanes and sticks while the page scrolls, with a height that fits the window. Below 820 px it stacks above the lanes as before.
  • The README and the app.js header describe the new layout.

CSS and comments only. No change to stages.js or to the document format.

Test plan

  • python3 -m unittest test_viewer in tools/dag-viewer (with py-mini-racer): all tests OK, none skipped.
  • The published Stage Viewer artifact uses the same page and shows the stacked lanes.

🤖 Generated with Claude Code

Stage 0, Stage 1 and Stage 2 now sit one below the other, each as wide as
the page allows, so a wide DAG is readable without squeezing three lanes
side by side. The Stage 3 list stays beside them and sticks while the page
scrolls; on a phone it stacks above as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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