-
Notifications
You must be signed in to change notification settings - Fork 85
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
fix: only set err.status on statusCode >= 200 #677
Conversation
WalkthroughThe primary change involves updating the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration 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
Out of diff range and nitpick comments (1)
app/port/middleware/ErrorHandler.ts (1)
34-34
: The logic to ensurectx.status
is only set whenerr.status
is a valid HTTP status code is correctly implemented.Consider adding a comment explaining why the status code check is necessary, as this could enhance maintainability and understanding for future developers.
[skip ci] ## [3.56.1](v3.56.0...v3.56.1) (2024-05-14) ### Bug Fixes * only set err.status on statusCode >= 200 ([#677](#677)) ([668eed2](668eed2))
Summary by CodeRabbit