Invalid exclusive{Maximum|Minimum} values in groundhog-day about openapi-directory HOT 8 CLOSED

openaq.local/2.0.0 Has a similar issue (just true instead of false):
https://github.com/APIs-guru/openapi-directory/blob/main/APIs/openaq.local/2.0.0/openapi.yaml#L52

from openapi-directory.

So does shipengine: https://github.com/APIs-guru/openapi-directory/blob/main/APIs/shipengine.com/1.1.202304191404/openapi.yaml#L10746

from openapi-directory.

As does linqr:

from openapi-directory.

And svix:

from openapi-directory.

daniweb:

from openapi-directory.

alertersystem: https://github.com/APIs-guru/openapi-directory/blob/433a94f3e9e268f2b000b0b497785ede34332a7f/APIs/alertersystem.com/1.7.0/openapi.yaml#L42168

from openapi-directory.

plaid: https://github.com/APIs-guru/openapi-directory/blob/433a94f3e9e268f2b000b0b497785ede34332a7f/APIs/plaid.com/2020-09-14_1.345.1/openapi.yaml#L31780

from openapi-directory.

Turns out the meaning of exclusiveMinimum and exclusiveMaximum has changed in a later draft, and I missed that these openapi documents were based on openapi 3.0.x which still used the wright-json-schema-validation draft.

In that draft these properties must be booleans: https://datatracker.ietf.org/doc/html/draft-wright-json-schema-validation-00#section-5.3

Sorry for the noise.

from openapi-directory.