exclusiveMaximum / exclusiveMinimum rabbit hole

[jandppw]

The addition of exclusiveMaximum / exclusiveMinimum to negative / positive number type schemata in v4.1.0 opens up a rabbit hole.

When using joi-to-json to generate OpenAPI models, the result conflicts with current @redocly/cli schema validation, e.g.,

[67] […]

Example validation errored: exclusiveMinimum value must be ["number"].

 8 |   required: true
 9 |   schema:
10 |     minimum: 0
11 |     exclusiveMinimum: true
 … |     < 5 more lines >
17 |     example: 1
18 | - name: planLabel
19 |   in: path

This is because of a non-backward compatible (!) change from OpenAPI 3.0 to OpenAPI 3.1, as described in ExclusiveMinimum and ExclusiveMaximum.

According to the README of joi-to-json, joi-to-json targets “open-api - Stands for OpenAPI 3.0 Schema […]’, so this is not a bug in joi-to-json, but rather in redocly lint (see Redocly/redoc#2467), but the issue might be worth some consideration.

See, e.g., astm-utm/Protocol#65 for the rabbit hole.

[kenspirit]

@jandppw Thanks for the reminder. I was not aware of the 3.1 incompatible change before. I have added a separate format support for OpenAPI 3.1 spec in case anyone needs it.

[jandppw]

Damn, that’s fast! 🤩

I will probably not be able to use the new version before the start of next year, but I’m sure it will solve the issue.

Thank you very much!