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.
Currently, only
multipart/form-data
is supported by multipart handling.While this is probably the most important use case, also
multipart/mixed
is quite common, e.g. in REST APIs.I recently struggled with batch requesting a SharepointOnline list and finally found my way through it. I thought, I could share my experience with the community and propose this PR.
If this seems useful to the maintainers, I'll happily provide also some test routines.
In order to add the mixed functionality I added a field
type
to theForm
object and I added a bypass for content_disposition check, because that is not present for mixed type multiparts.Furthermore, I added
parse_multipart()
as a general parsing method, which automatically choses the correct parsing method from the type field.Finally I added a type-based and a handler-based parsing interface for users and a predefined parser for Responses.
Here is the intended usage of the new feature