-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write a serializer for multipart encoded forms #5022
Comments
@humitos |
@dojutsu-user well, I don't exactly know how to do it since I've never done it before, but the documentation linked in the description should guide you. When instantiating the client, it passes the serializer:
|
@humitos So, may be we won't be able to do this with slumber. |
Yeah, you are right. Blocking on samgiles/slumber#148 We could install that particular commit/revision in case we really want to do it like this since the project looks kind of dead unfortunately :( |
I'm also fine working around slumber for this, though the current solution is a little hacky. |
In #5000 we are manually manipulating the request to send the data using
MultipartEncoder
directly to avoid an issue that we found when sending large data.The proposal is a solution, but we think it could be cleaner if we write a Slumber serializer and we use it directly instead of touching the request at that level: https://slumber.readthedocs.io/en/v0.6.0/options.html#serializer
Also, once this serializer is written and tested, we need to double check if #5021 disappears with the usage of a serializer.
The text was updated successfully, but these errors were encountered: