Mike Ralphson

There is a new version in the works.

Are you sure it's not indentation / `{` `[` mismatches (as above in red) which are causing your issues. This project isn't opinionated about `type` being present AFAIR.

I wonder if it's the presence of `default` without a direct sibling `type` that is triggering a rule for OAS 3.0 that defaults must be of the right type. What...

I've corrected the OpenAPI syntax and confirmed that it is the presence of `default` that is triggering the error. In this case you/the OP should move the `default` into the...

One thing you could do is set `options.laxDefaults` to `true`, as per https://github.com/Mermade/oas-kit/blob/main/docs/options.md#options-documentation

Could you expand on why this behaviour was acceptable in OpenAPI 2.0 (it doesn't seem obvious to me). Optional and nullable mean different things here. My gut feeling is this...

See https://github.com/limulus/call-me-maybe for one potential solution.

https://github.com/olado/olado.github.com

I think you're right, maybe a warning. In APIs.guru we have an extension `x-hasEquivalentPaths` (https://github.com/APIs-guru/openapi-directory/wiki/specification-extensions#x-hasequivalentpaths) which we use to tag the output of other converters (like Google discovery format) to...

Agree, the possible combinations of templated variables probably make this an intractable problem, and that's just for `servers.url`, I'm unsure if Postman env. variables can be used only in specific...