Conversation
… light theme Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
OperationResultNoticesuccess/error tones used hardcoded darkoklchvalues, leaving dark text on a dark panel in light mode. Swapped them for--color-success-*/--color-error-*CSS variables defined per-theme inglobals.css.<Toaster />was rendering with its default theme regardless of the app theme. Now passes the activethemefromuseTheme()and enablesrichColorsso success/error toasts use proper contrast in both modes.useThemeto useuseSyncExternalStore<Theme>so the returned value stays narrowed to"light" | "dark"(needed for the newToasterprop).