chore: suppress deprecation warnings in tests for deprecated console API#1764
Conversation
Test classes that intentionally exercise the deprecated org.jline.console API (replaced by org.jline.shell in 4.0) now have @SuppressWarnings("deprecation") to keep the build warning-free. The new API has its own test coverage in the shell module.
|
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 10 minutes and 7 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|



Summary
@SuppressWarnings("deprecation")to 3 test classes that intentionally use the deprecatedorg.jline.consoleAPI (replaced byorg.jline.shellin 4.0)SystemRegistryImplTest,Consoleexample,PicocliCommandRegistryTestorg.jline.shellAPI already has its own test coverage (ArgumentDescriptionTest,CommandDescriptionTest,CommandLineTest,ShellBuilderTest)Test plan