fix(cli): validate --exclude regex pattern before use#262
fix(cli): validate --exclude regex pattern before use#262evanofficial wants to merge 1 commit intorafaeltonholo:mainfrom
Conversation
Invalid regex patterns passed to --exclude caused an unhandled
PatternSyntaxException with a stack trace. Now validates the
pattern early using Clikt's validate {} and shows a clear error.
Closes rafaeltonholo#239
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 14 minutes and 59 seconds. ⌛ 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
Closing — just noticed #251 already addresses this. Apologies for the duplicate! |
Summary
Invalid regex patterns passed to
--excludecaused an unhandledPatternSyntaxExceptionwith a raw stack trace. Now the pattern is validated early using Clikt'svalidate {}block, displaying a clear error message instead.Before:
After:
Changes
Main.kt— Added.validate {}on the--excludeoption that wrapsRegex()in a try-catch and callsfail()with a descriptive messageCloses #239