-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure $schema
properties start with http
not https
#44
Comments
So I looked into this a bit. Firstly, it already works for us through 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 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. |
Reverted. Not going to fix this because it breaks the |
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
The text was updated successfully, but these errors were encountered: