Improved bundle documentation#27
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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
Pre-1.0 documentation pass: name the bundle's public API surface in the README, add a single page covering each extension point with a worked example, and clarify the two validation layers up front in the validation guide.
Changes
@apiitems, plus a "Two-Layer Validation" feature bullet that names both the OpenAPI schema layer and the Symfony Validator layer.ValidatorInterface,ResponderInterface,StatusResolverInterface,ExceptionToApiProblemTransformerInterface, plus how to throwApiProblemExceptiondirectly. Includes an architectural note thatApiProblemExceptionis HTTP-layer and shouldn't be thrown from handlers.