Use https://
references in JSON schemas
#451
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All of the other DIF schemas are using
https://
references to other schemas, not sure why the case is here thathttp://
was used, but I think that should be changed. This is because validators can consider these two different schemas causing potentially two downloads and two compilings of the schemas. For us as we plan on having the schemas locally (not downloadable), we either have to have two entries or make local workaround (that replaces the http with https).This PR is fixing this issue for this package schemas.