Fix error response bug#224
Merged
Merged
Conversation
david-crespo
commented
Dec 2, 2023
| const { body, bodyErr } = bodySchema | ||
| ? validateBody(bodySchema, await req.json()) | ||
| : { body: undefined, bodyErr: undefined }; | ||
| if (bodyErr) return json(bodyErr, { status: 400 }); |
Collaborator
Author
There was a problem hiding this comment.
bodyErr is already a Response, so we were seeing {} as the response body in the browser because JSON.stringify(new Response()) == '{}'.
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
1 participant
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.
Tiny bug introduced in #215, only affected error response on mock server, which we didn't notice because we pretty much only ever see zod error responses when inspecting a mock error response manually in the browser network tab.