Skip to content

feat(display/tui/style): AdaptiveColor seam (the lipgloss-v2 gap for charm-free cli/tui)#34

Merged
Snider merged 1 commit into
mainfrom
lane/style-adaptivecolor
Jul 23, 2026
Merged

feat(display/tui/style): AdaptiveColor seam (the lipgloss-v2 gap for charm-free cli/tui)#34
Snider merged 1 commit into
mainfrom
lane/style-adaptivecolor

Conversation

@Snider

@Snider Snider commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

The one provider gap the charm-free coverage probe found. lipgloss v2 deleted AdaptiveColor; this restores it as style.AdaptiveColor{Light, Dark string} + Resolve(isDark) Paint (delegating to the existing NewLightDark), so go-inference's cli/tui theme keeps its shape through the v1→v2 swap. Additive; 23 style tests pass (+3 +1 Example), gofmt/vet clean.

🤖 Generated with Claude Code
Co-Authored-By: Virgil virgil@lethean.io

… v2 dropped

lipgloss v2 removed the v1 AdaptiveColor type (implicit light/dark adaptation)
in favour of an explicit isDark resolve. This restores the paired shape as
data — AdaptiveColor{Light, Dark string} + Resolve(isDark) delegating to
NewLightDark — so a consumer's theme keeps its v1 shape and adds one resolve
step per frame. Unblocks go-inference cli/tui's charm-free migration
(10-field theme, 22 paint sites). One test per variant + an Example.

Co-Authored-By: Virgil <virgil@lethean.io>
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 4 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: CHILL

Plan: Pro Plus

Run ID: f7e2a435-df35-4878-92b4-a89b183d3c8e

📥 Commits

Reviewing files that changed from the base of the PR and between 38eb393 and 4b7fe0d.

📒 Files selected for processing (3)
  • go/display/tui/style/color.go
  • go/display/tui/style/color_test.go
  • go/display/tui/style/example_test.go

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


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.

❤️ Share

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

@Snider
Snider merged commit bcee2e8 into main Jul 23, 2026
2 checks passed
@sonarqubecloud

Copy link
Copy Markdown

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