fix: #43 use custom content type parser for application/json and text/plain #44
Conversation
This file contains 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
So that changes to the Fastify instance will only be reflected in each plugin's scope.
…/plain Pipe the request stream for these content types instead of the default handling. See https://www.fastify.io/docs/latest/ContentTypeParser/.
thebengeu
force-pushed
the
fix/43_content_type_parser
branch
from
db0dff2
to
d36e32a
Compare
|
Nice @thebengeu 🔥 |
inian
approved these changes
Jul 15, 2021
|
🎉 This PR is included in version 0.7.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
What kind of change does this PR introduce?
Pipe the request stream for these content types instead of the default handling. See https://www.fastify.io/docs/latest/ContentTypeParser/.
What is the current behavior?
text/plainandapplication/jsonMIME type are uploaded in Storage Buckets as empty files.What is the new behavior?
text/plainandapplication/jsonMIME type are uploaded in Storage Buckets correctly.