Content header is not properly set as default for objects in multipart resquests.
To reproduce...
Steps to reproduce the behavior:
Paste provided def into editor
Click on endpoint (expand view)
Shouldn't there be something to view schema (next to example data button) like displayed in figure 1? It's missing as seen in figure 2.
If you hit execute now, following curl command is suggested (which doensn't work with generated java code):
Executing curl command fails because default content-type is application/octet-stream, which is rejected by a properly configured REST Api.
Further, I'd expect a schema view for request body, which works if just changing 'multipart/form-data' to 'application/json' in given definition. Adding encoding for parameter manually adds correct header.
Q&A (please complete the following information)
Content & configuration
Using online editor (or local spring boot swagger UI installation) with following definition:
Swagger-Editor configuration options: doesn't apply (online editor defaults)
Describe the bug you're encountering
Content header is not properly set as default for objects in multipart resquests.
To reproduce...
Steps to reproduce the behavior:
Where I expect:
Expected behavior
Executing curl command fails because default content-type is application/octet-stream, which is rejected by a properly configured REST Api. Further, I'd expect a schema view for request body, which works if just changing 'multipart/form-data' to 'application/json' in given definition. Adding encoding for parameter manually adds correct header.
Screenshots
Additional context or thoughts
Maybe related to https://github.com/swagger-api/swagger-editor/issues/4609