Semantic error at ... Schema "type" key must be a string

With Swagger Editor 3.5 when opening a Swagger 2.0 description containing constructs such as

    type: object
    properties:
      KeyDate:
        type:
          - string
          - 'null'

I get the error message above.

Opening the same file with Swagger Editor 2.10.5 works fine, as does opening it with Swagger UI 2.x and the latest Swagger UI 3.x.

This seems to be a regression.

Is it planned to be fixed?

[ralfhandl]

@shockey cool, works like a charm 😄

[shockey]

@ralfhandl awesome! Just one more note from me here…

With Swagger Editor 3.x not accepting content that is accepted by Swagger Editor 2.x migration fails in step 1.

Note that Swagger Editor doesn’t bar you from doing much of anything based on the validity of your definition - you can still save, Try-It-Out, and use the Codegen service.

We add new validators fairly frequently, and we’ll probably never have a complete set of them. OpenAPI has upwards of 30 object types, many of which nest inside of one another, so there’s a large set of things that we could validate for, that we haven’t validated against yet.

We never tag new validators (even error-level validators) as breaking changes, our stance is that we only support fully spec-compliant (as opposed to previously-validator-compliant) definitions. I know it’s not any fun to think you have a good OpenAPI document one day, and have it flagged the next, but given the problem space that our validators cover it’s the best experience that we can provide at this time.

Hopefully this sheds some light on why we do things this way 😄