Repository navigation
fix(validator): read multipart and URL-encoded bodies - #748
Merged
Merged
Conversation
withValidator parses form bodies through parseBody, restores bracketed fields as nested objects and arrays, and leaves JSON bodies on json().
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
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.
Fixes #679
Description
withValidator({ body })only calledc.req.json(), so auseForm/action()upload (multipart/form-data) returned 400 before the handler. Multipart and urlencoded bodies are now parsed as form data. Bracket keys are restored to nested objects and arrays, andFilevalues reach the schema. Booleans, numbers, dates, and null stay in the form encoding, so a multipart schema needs coercion. JSON bodies are unchanged.Test