Reuse enum definition multiple times

Enum in generated OpenAPI document is defined inline.

  "schemas": {
    "myRequest": {
(...)
      "properties": {
        "myEnumProperty": {
          "enum": [
            "value1",
            "value2"
          ],
          "type": "string",
(...)

When using an enum multiple times within the same API, Visual Studio ‘Connected Services’ (utilizing nswag) will generate multiple enum definitions on client-side for the same enum. This requires uneccessary type conversions in client code.

OpenAPI spec allows to define enum as reference, which results in only one enum definition on client-side:

  "schemas": {
    "myEnumType": {
      "enum": [
        "value1",
        "value2"
      ],
      "type": "string",
(...)
    },
    "myRequest": {
(...)
      "properties": {
        "myEnumProperty": {
          "$ref": "#/components/schemas/myEnumType"
        }
(...)

Is it possible to configure enum gerenation as reference?

Would be a great help.

[AllTaken]

@level120 Having this work as long as enum names are unique would already add a lot of value…

[HermannGruber]

I guess I’m facing the same issue. I have an azure function, for which the generated swagger.json looks similar as above, but I want to have the enums defined once and then referenced. Currently it reads

{
            "name": "pruefungszeitpunkt",
            "in": "query",
            "description": "Prüfungszeitpunkt",
            "schema": {
              "enum": [
                "beiKodierung",
                "zurAbrechnung",
                "waehlbar"
              ],
              "type": "string",
              "default": "beiKodierung"
            },
            "x-ms-visibility": "important"
          }

But I would like to see

          {
            "name": "pruefungszeitpunkt",
            "in": "query",
            "description": "Prüfungszeitpunkt",
            "schema": {
              "$ref": "#/components/schemas/Pruefungszeitpunkt",
              "type": "string"
            },
            "x-ms-visibility": "important"
          },

Can you please tell me whether this will be resolved using the current issue? If not, I will happily open a separate issue. (My generated swagger.json says at the top of the file that it is targeting OpenApi 3.0.1.)