This repository was archived by the owner on Mar 18, 2019. It is now read-only.
Description When attempting to document an API which uses header based versioning, I'm running into issues with errors like the following:
{
"detail" : " Could not satisfy the request Accept header."
}
When attempting to use "try it out" in the swagger UI.
After much debugging, I determined this is the source of the issue:
https://github.com/core-api/python-openapi-codec/blob/master/openapi_codec/encode.py#L78
Consumes is populated, but produces is NOT populated. We managed to get a "workaround" in play by manually patching it:
from openapi_codec import encode
old_get_operation = encode ._get_operation
def patch_get_operation (operation_id , link , tags ):
operation = old_get_operation (operation_id , link , tags )
operation ["produces" ] = ["application/vnd.acme.v2+json" ]
return operation
Is there a plan in the roadmap to implement this aspect of the swagger spec ?
Reactions are currently unavailable
When attempting to document an API which uses header based versioning, I'm running into issues with errors like the following:
{ "detail": "Could not satisfy the request Accept header." }When attempting to use "try it out" in the swagger UI.
After much debugging, I determined this is the source of the issue:
https://github.com/core-api/python-openapi-codec/blob/master/openapi_codec/encode.py#L78
Consumes is populated, but
producesis NOT populated. We managed to get a "workaround" in play by manually patching it:Is there a plan in the roadmap to implement this aspect of the swagger spec?