Fix causal footer and gutter posture - #204
Conversation
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (18)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 223579c18a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const BASIS_CELL_WIDTH = 14; | ||
| const HEAD_CELL_WIDTH = 5; | ||
| const DELTA_CELL_WIDTH = 9; | ||
| const SPAN_CELL_WIDTH = 9; |
There was a problem hiding this comment.
Widen the span column to preserve tick ranges
When a node has different basis/head ticks, workspaceWorldlineTickSpanLabel(node) can return labels like ticks:t0->t10 (13 characters), but this new column is capped at 9 characters and cell(row.span, SPAN_CELL_WIDTH) truncates it before the drawer is fit to the terminal. In any history with a multi-digit canonical tick or a braid spanning from an older basis to a later head, the phase drawer drops the head tick from the causal span, making the displayed posture inaccurate even on wide terminals.
Useful? React with 👍 / 👎.
Summary
Verification
Notes
Follow-up to the dogfooding issues raised around causal footer posture, gutter theming, and unreadable light-theme text.