Fixing response documentation for OpenAPI 3.x

[rusnyder]

Currently, the responses OpenAPI docs are generated in OpenAPI 2.0 format regardless of specified version. This just updated the responses formatting to handle OpenAPI 3.0 appropriately.

OpenAPI 2.0:

produces:
  - application/json
responses:
  200:
    description: 'Some response'
    schema:
      $ref: "#/definitions/SomeSchema"

OpenAPI 3.0:

responses:
  200:
    description: 'Some response'
    content:
      application/json:
        schema:
          $ref: "#/definitions/SomeSchema"

[playpauseandstop]

Hi flask-apispec maintainers,

It would be really great if you'll find time to review given MR.

As @rusnyder perfectly described there are some differences in Swagger 2.0 & OpenAPI Schema 3.0 response definition and currently, with flask-apispec==0.9.0, there is no chance to make valid OpenAPI 3.0 schema as flask-apispec still uses Swagger 2.0 responses definitions.

Thanks in advance!

---

Hi @rusnyder,

I understand, that you might be off topic already, but what do you think about allowing configuring default content type for the app instead of using default application/json here,

content_type = meta['content_type'] or 'application/json'

Something like APISPEC_DEFAULT_CONTENT_TYPE config var seems reasonable for me. What do you think?

[tedblad]

How come this hasn't been merged yet?

[zastruga]

Bump. It would appear the maintainer has left the building.

[quantrung9]

Please merge this 😅

[quantrung9]

@rusnyder I think it would be better if you use the get method to get the data so that it won't get errors when content_type does not exist in the meta. Something like this:

content_type = meta.get('content_type') or 'application/json'