Pedro J. Molina

Two cents on this. To support CORS, we are using the following middleware when needed: https://github.com/Icinetic/model-101/blob/master/app/services/authz.js#L37-L44 ``` //CORS enabled for allowing 3rd party web-apps to consume Swagger metadata and backend....

Do it works on a previous version of node? Could you share a minimal sample code to reproduce it?

+1 - Bug reproduced also with node `v9.8.0` - Works OK on `v.8.0.0`

You nailed it @tedepstein ! It looks like we have experience the same kind of pain. ;-)

Fair point @MikeRalphson : - External $refs can be resolved (imported) to be local. - Local $ref may be considered to be inside the **Canonical Form** if needed (this usage...

True, the semantics of the Extended Form should generate a unique Canonical Form. Moreover, we can provide a Test Suite to illustrate the expected input + expected output.

Looks like the change is coming from different versions of JSON Schema. OpenAPI is not redefining them, but using them directly from JSON Schema. See: https://json-schema.org/understanding-json-schema/reference/numeric.html - Previous versions used...

Indeed, we can enforce 3.1.0 but also thinking about relaxing the type for `exclusiveMaximum` and `exclusiveMinimum` to be `number | boolean` to help people to transition from OpenAPI 3.0 (boolean)...

> Also, which tool would you recommend to validate 3.1 specification? A good list of validators and compatibility is maintained here: https://openapi.tools/#data-validators Support for 3.1 has a "slow adoption" so...

Thanks for the time taken to prepare and example @svrakata (we can use it as the seed for minimal docs). As you all know, documentation like any other feature requires...