We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An API call may be able to consume multiple formats. This format could be for example multipart/form-data or application/json.
multipart/form-data
application/json
However, following the spec, these fields are mutually exclusive. The following is considered invalid by Swagger editor:
info: title: demo version: 1.0.0 paths: /: post: consumes: - application/json - multipart/form-data parameters: - name: payload in: body schema: {} - name: attachment in: formData type: string responses: 200: description: asd swagger: '2.0'
The text was updated successfully, but these errors were encountered:
V3.0 of the spec introduces a new requestBody object and this PR #761 changes the way media types are mapped to request/response bodies.
Sorry, something went wrong.
@remcohaszing Can I close this? I do believe OpenAPI 3.0 will address this requirement.
No branches or pull requests
An API call may be able to consume multiple formats. This format could be for example
multipart/form-data
orapplication/json
.However, following the spec, these fields are mutually exclusive. The following is considered invalid by Swagger editor:
The text was updated successfully, but these errors were encountered: