Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request reworks error title rendering in the error display component to support multi-line titles. The implementation adds width-based wrapping logic using UTF-8 rune counting, renders the first wrapped line with a "✗ " prefix, and indents subsequent lines with spaces for alignment. An accompanying test validates that wrapped titles stay within the specified width. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@internal/ui/components/error_display_test.go`:
- Around line 101-106: The width assertion is counting ANSI styling from
styles.ErrorTitle.Render(), making len([]rune(line)) unreliable; update the test
to either strip ANSI escape codes before measuring or test the wrapping logic
directly by calling wrap.SoftWrap (or the equivalent wrapping function) on the
raw unstyled text and assert its widths, and keep
View()/styles.ErrorTitle.Render() assertions limited to content presence; locate
the check in error_display_test.go that iterates over lines and modify it to
remove ANSI sequences (or replace the loop with a call to wrap.SoftWrap on the
unstyled string) before using len([]rune(...)) so the assertion reflects visible
width only.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: 8cf9123f-cb60-4fd8-8851-5ababb6e21af
📒 Files selected for processing (2)
internal/ui/components/error_display.gointernal/ui/components/error_display_test.go
2c3ad73 to
d54b02a
Compare
|
Thanks for taking a look, @carole-lavillonniere! 🍿 |
This will:
✗prefix to get correct indentation on continuation lines