We are using SwashBuckle 5.0 and trying to produce a swagger doc 2.0. And apparently it does produce swagger.json which is not 100% compliant with swagger 2.0 specs. The problem is specifically around how it does enlists the enums:
name: prop-name
description: something
type: array
items:
$ref: '#/definitions/mytype'
where it should had been :
name: prop-name
description: something
type: array
items:
type: string
enum:
- Item1
For it to be 100% swagger 2.0 spec.So jus tto summarize, SwashBuckle has produced a swagger.json for us which is not 100% swagger 2.0 complaint. We are enforcing our configuration to use V2 by spefically saying SerializeAsV2 = true
We also considered upgrading to OAS 3.0 and decided against to for now since all of the clients have to change and it is a big effort. So we are back to trying to figure out how can have have SwashBuckle produce a swagger.json that is 100% swagger 2.0 complaint? I just want to see if there is not a configuration that we need to change before I file a bug against SwashBuckle team.
Any suggestions?