Skip to content

[US-8.3 / OBT-215] Move dependency management into a dialog - #23

Open
levigtri wants to merge 2 commits into
mainfrom
levigft/obt-215-us-83-the-dependency-management-ui-to-not-take-up-permanent
Open

[US-8.3 / OBT-215] Move dependency management into a dialog#23
levigtri wants to merge 2 commits into
mainfrom
levigft/obt-215-us-83-the-dependency-management-ui-to-not-take-up-permanent

Conversation

@levigtri

@levigtri levigtri commented Jul 5, 2026

Copy link
Copy Markdown
Member

Summary

US-8.3 / OBT-215 — The dependency management UI no longer occupies a permanent column on the phases page, so the page feels less cluttered and gives more room to the table and graph.

Changes

  1. PhasesPage.tsx: remove the 2-column grid. The page is now a single full-width column (dependency graph + phases table). Selecting a phase — by clicking a table row or a graph node — opens a dialog to manage that phase's dependencies. Closing the dialog clears the selection.
  2. phases/DependencyPanel.tsx: drop the standalone card.padded wrapper and the redundant per-phase heading, since it now renders inside the dialog.

Type of Change

  • Refactor / UX

Testing

  • npm run typecheck — pass
  • npm run lint — 0 errors (pre-existing ProjectsPage warning only)
  • npm run build — pass

Front-only. The read-only phase description in this dialog (US-8.1) is stacked on top of this branch.

Remove the permanent right-hand dependency column. The phases page now uses a
single full-width layout (graph + table), and selecting a phase — from the table
row or a graph node — opens a dialog to manage its dependencies. The
DependencyPanel drops its standalone card wrapper since it now lives in the modal.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@levigtri, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Pro Plus

Run ID: 1087dda4-1bac-4787-bb14-acaf5e53bc4b

📥 Commits

Reviewing files that changed from the base of the PR and between 130fc4a and 3c63b98.

📒 Files selected for processing (2)
  • src/components/pages/PhasesPage.tsx
  • src/components/pages/phases/DependencyPanel.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch levigft/obt-215-us-83-the-dependency-management-ui-to-not-take-up-permanent

Comment @coderabbitai help to get the list of available commands.

@levigtri levigtri self-assigned this Jul 15, 2026
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