[Fix] - Handle filestream json data in multipart/form-data requests #65
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
cgearing
force-pushed
the
fix/handle-binary-json-payloads-in-multipart-form
branch
from
76b3c7a to
7be8a75
Compare
cgearing
force-pushed
the
fix/handle-binary-json-payloads-in-multipart-form
branch
from
7be8a75 to
7ab5ad8
Compare
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.
This PR fixes an issue we have seen with some OpenAPI client generators where for a multipart/form-data payload, they are sending a binary object with a content-type attached. This PR handles this where we find it in the files section of the request, adding these to the body to be validated by Pydantic.