You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 21, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 21, 2024. It is now read-only.
When using JSON schema in RAML types the $schema property doesn't appear to be respected. Back in JSON schema Draft 4 the exclusiveMaximum property was a boolean, it was updated to be an integer in later draft revisions (see: https://json-schema.org/understanding-json-schema/reference/numeric.html#range). However when I run the webapi-parser's validate function on my RAML I get an error that says exclusiveMaximum should be of type boolean, not integer.
Is this a bug with the parser, or is there a way I can force the parser to either respect the $schema property or specify what draft I want it to validate with?
Looks like our dependency lib now supports JSON Schemas up to draft 7. We are currently working on updating our lib as well. I'll let you know when the new version is available.
Activity
postatum commentedon Dec 20, 2019
Hi @bloche.
It's a limitation of our dependency lib
AMF. I've created a gh issue and requested more drafts to be supported.I'll let you know when we release a new version of
webapi-parserwith newer json schema versions supported.bloche commentedon Dec 20, 2019
Thanks @postatum
postatum commentedon Jun 19, 2020
Hi @bloche.
Looks like our dependency lib now supports JSON Schemas up to draft 7. We are currently working on updating our lib as well. I'll let you know when the new version is available.
bloche commentedon Jun 20, 2020
@postatum That's great to hear, thanks for keeping me informed.