fix: return 400 instead of 500 for malformed JSON body in POST /api/bounties - #512
Merged
Merged
Conversation
…ounties Handle JSON parse failures explicitly before schema validation. Previously, request.json() threw inside the broad error handler which returned 500. Now returns 400 with 'Malformed JSON body' message. Closes profullstack#509
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
POST /api/bountiesreturns HTTP 500 for malformed JSON becauserequest.json()throws inside the broad error handler.Fix
Added inner try/catch around
request.json()that returns HTTP 400 before reaching schema validation or the database.Changes
route.ts: Catch JSON parse errors explicitlyroute.test.ts: Added regression testTest
Closes #509