Closed annakrystalli closed 11 months ago
So I looked into this a bit.
Firstly, it already works for us through jsonvalidate
R package and when I looked at the json-schema.org docs on declaring a JSON schema, the example uses https
🤷♀️
It looks like this is an ajv issue (e.g. see here which emanates from the fact that that ajv bundles the meta schema up, treats the $schema
property an identifier to a bundled file (it is not retrieved from the net) and does not recognise https.
So I wasn't sure whether to bother with this as it doesn't affect our workflow. But given it may make the schema files more interoperable with other validation tools, I'll go ahead and implement it.
Oddly, shifting to http
now causes the same error when using jsonvalidate
in R 🤷♀️
Reverted. Not going to fix this because it breaks the jsonvalidate
workflow
URLs which start with
https
are not recognised byajv
causing issues when using other validators likeajv-cli
. So all URLs in$schema
properties specified the json schema version should start withhttp
.See issues brought up in #42