Inject input into confirmApply instead of hardcoding os.Stdin#22
Conversation
confirmApply now accepts an io.Reader parameter threaded from the command boundary via cmd.InOrStdin(). This makes the confirmation flow testable with injected input and reusable in non-interactive integrations. Closes #11 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
Summary
confirmApplynow accepts anio.Readerparameter instead of hardcodingos.Stdin.cmd.InOrStdin().Test plan
TestConfirmApplyFromInjectedInput— table-driven tests for "y", "YES", "n", and empty inputcmd.InOrStdin()make verifypassesCloses #11
🤖 Generated with Claude Code