-
Notifications
You must be signed in to change notification settings - Fork 143
Enhance validation error handling with custom exception messages #1044
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughA custom Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant App
participant ValidationPipe
participant exceptionFactory
Client->>App: Send request with payload
App->>ValidationPipe: Validate payload
ValidationPipe->>exceptionFactory: On validation error, call exceptionFactory(errors)
exceptionFactory->>ValidationPipe: Return BadRequestException with aggregated message
ValidationPipe->>App: Throw BadRequestException
App->>Client: Respond with aggregated error message
Poem
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
api/src/main.ts (1)
74-83
: Good implementation that achieves the PR objectives!The custom exception factory successfully aggregates validation errors into user-friendly messages. The fallback message handling is a nice touch.
Consider these optional enhancements for even better error reporting:
- Include the invalid value in fallback messages for easier debugging:
- return `${error.property} has invalid value`; + return `${error.property} has invalid value: ${error.value}`;
- Return structured error responses for better API consumer experience:
- return new BadRequestException(messages.join(', ')); + return new BadRequestException({ + message: 'Validation failed', + errors: messages + });The current implementation works well for the stated objectives of providing clearer validation feedback.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
api/src/main.ts
(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Frontend Tests
- GitHub Check: API-Tests
- GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (1)
api/src/main.ts (1)
9-9
: Import looks good!The addition of
BadRequestException
is necessary for the custom exception factory implementation.
Improve validation error handling by introducing custom exception messages that provide clearer feedback on validation failures.
Summary by CodeRabbit