Support multi content type in request body and responses #214
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.
Checklist:
pytest tests
and no failed.ruff check flask_openapi3 tests examples
and no failed.mypy flask_openapi3
and no failed.mkdocs serve
and no failed.Many people have multi content-type needs:
Here is a solution that can specify different content types for each class.
As a result, some break changes had to be generated:
openapi_extra
no longer supportsdescription
andrequired
in request body, and instead usesrequest_body_description
andrequest_body_required
.openapi_extra
no longer supportsdescription
,headers
andlinks
in response, and replace with the following form.