fix: preserve existing request body fields#1399
Open
raashish1601 wants to merge 1 commit into
Open
Conversation
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.
Summary
Preserve existing own
req.bodyproperties when Multer initializes multipart parsing, instead of replacing them with an empty object.Multer still uses a null-prototype object for
req.body; it copies existing own enumerable properties into that object before appending multipart fields.Fixes #1187.
Validation
npm run lintnpx mocha --reporter spec --exit --check-leaks test/fields.jsI also ran
npm test; it reached the new regression successfully, but the full suite fails in this Windows checkout on existing fixture byte-size and POSIX path assertions unrelated to this change, for example1803 !== 1778in storage/file size tests and/testforme-path matching.