-
Notifications
You must be signed in to change notification settings - Fork 758
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
Missing individual parts content-types in multipart/formdata
requests.
#2954
Comments
I created a draft PR addessing this issue. I could use some help, since this would be my first contribution. #2955 |
@char0n Could you take a look at this, please? I have zero familiarity with the project but I really want to fix this bug. Can you give me some guidance on the draft PR? |
Hi @mateusbandeiraa, all right, let me have a look. And thanks for contributing! |
@mateusbandeiraa can you also please provide the actual code that reproduces this issue? I need an example which I can run and see the results you're describing. |
This change affects building requests from OpenAPI 3.x.y definitions. Refs swagger-api/swagger-ui#5356 Refs swagger-api/swagger-ui#4826 Refs #2954
Addressed in #3078 |
Q&A (please complete the following information)
Content & configuration
Swagger/OpenAPI definition:
Swagger-Client usage:
Describe the bug you're encountering
To reproduce...
Steps to reproduce the behavior:
POST /api/v1/profile
withavatar_image
as a png file, andprofile
as a JSON stringExpected behavior
The generated request body should be:
(notice
Content-Type: application/json
in the profile part)Actual behavior
The actual generated request body is:
(notice the missing
Content-Type: application/json
in the profile part)Additional context or thoughts
This issue was initially created as swagger-api/swagger-ui#5356, but the required code change to fix this issue is in this repository.
The text was updated successfully, but these errors were encountered: