feat: add structured error responses with error classes and handler tests#449
Conversation
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus 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 |
Welcome to OSSfolio, @DebasmitaBose0! 🎉Thank you for opening this pull request and contributing to the open-source community! 🚀 To ensure a smooth review process, please make sure you have:
We will review your PR as soon as possible. Happy coding! 💻✨ |
|
🎉 Your PR just got merged, @DebasmitaBose0 — thank you for contributing to OSSfolio! Your work is now part of the project. Here's what to do next:
We really appreciate you taking the time. See you in the next PR! 🚀 |
Clsoes #421
Summary
Adds structured error responses with typed error classes, standardized error body format, and e2e tests for error shapes.
Changes
src/lib/errors.ts— new:AppError,ValidationError,AuthError,NotFoundError,RateLimitError,UpstreamErrorclasses;toApiErrorBody()for standardized shape ({ error, code, status, timestamp })src/lib/validators/api.ts—createErrorResponsenow emits{ error, code, status, timestamp }; addedapiErrorResponse()for AppError instances; addederrorCodeForStatus()mappinge2e/error-handling.spec.ts— tests for 400/404/429 error shapes, retryAfterSeconds, timestamp format