I'm interested in using quart-schema as a drop-in replacement for apiflask to generate OpenAPI documentation for my application.
So far, I've been able to use validate_response to generate relevant documentation for all of my application/json endpoints.
When it comes to my other content-types, such as text/event-stream, I've been able to successfully document the headers with Pydantic models with the signature:
Instead of documenting the response as application/json, I would like it to use the relevant literal from the Headers class that I've provided. I've added a simple test case to demonstrate.
I'm going to give this more consideration. I think Quart-Schema might benefit from a way to consider alternative/multiple content-types in a general sense.
I'm interested in using quart-schema as a drop-in replacement for apiflask to generate OpenAPI documentation for my application.
So far, I've been able to use
validate_response
to generate relevant documentation for all of myapplication/json
endpoints.When it comes to my other content-types, such as
text/event-stream
, I've been able to successfully document the headers with Pydantic models with the signature:However, this yields me the following OpenAPI docs:
Instead of documenting the response as
application/json
, I would like it to use the relevant literal from the Headers class that I've provided. I've added a simple test case to demonstrate.