The current loading / resource mechanism requires one to know all of the urls by defau

More importantly without having it affect the refs. <span class="e

you can override default resolver as follows: <div class="highlight highlight-sour

consider exposing a resolver that can handle any URL about jsonschema HOT 5 CLOSED

santhosh-tekuri commented on May 14, 2024

consider exposing a resolver that can handle any URL

from jsonschema.

Comments (5)

handrews commented on May 14, 2024

There are some clarifications on loading, caching, and referencing in the latest draft. I'm not 100% sure they are relevant as I'm not quite sure what the request is here, but it seems like it is related to providing different ways to load and cache schemas from various sources other than just looking at the URI scheme. e.g. loading schemas from the local FS even though the URIs have a scheme of https://.

from jsonschema.

gaffo commented on May 14, 2024

Yes that's a good summary, a way to load from various "repositories" more easily. Like a zip.

…

On Wed, May 23, 2018, 16:21 Henry Andrews ***@***.***> wrote: There are some clarifications on loading, caching, and referencing in the latest draft <https://tools.ietf.org/html/draft-handrews-json-schema-01#section-8.3>. I'm not 100% sure they are relevant as I'm not quite sure what the request is here, but it seems like it is related to providing different ways to load and cache schemas from various sources other than just looking at the URI scheme. e.g. loading schemas from the local FS even though the URIs have a scheme of https://. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAvLJJYSVqtsAsgwvKFTLNNz20veJf_ks5t1e7hgaJpZM4UK6Qm> .

from jsonschema.

gaffo commented on May 14, 2024

More importantly without having it affect the refs.

…

On Wed, May 23, 2018, 16:31 Mike Gaffney ***@***.***> wrote: Yes that's a good summary, a way to load from various "repositories" more easily. Like a zip. On Wed, May 23, 2018, 16:21 Henry Andrews ***@***.***> wrote: > There are some clarifications on loading, caching, and referencing in the latest > draft > <https://tools.ietf.org/html/draft-handrews-json-schema-01#section-8.3>. > I'm not 100% sure they are relevant as I'm not quite sure what the request > is here, but it seems like it is related to providing different ways to > load and cache schemas from various sources other than just looking at the > URI scheme. e.g. loading schemas from the local FS even though the URIs > have a scheme of https://. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#12 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAAvLJJYSVqtsAsgwvKFTLNNz20veJf_ks5t1e7hgaJpZM4UK6Qm> > . >

from jsonschema.

santhosh-tekuri commented on May 14, 2024

you can override default resolver as follows:

loader.Load = func(url string) (io.ReadCloser, error) {
    // TODO
}

from jsonschema.

santhosh-tekuri commented on May 14, 2024

FYI, loading schemas from the local FS even though the URIs have a scheme of https:// can be done without overriding resolver:

r, err := os.Open("schemas/test.json")
if err!=nil {
    panic(err)
}
err = compiler.AddResource("https://example.com/test.json", reader)

from jsonschema.

consider exposing a resolver that can handle any URL about jsonschema HOT 5 CLOSED

Comments (5)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent