diff options
| author | Julian Berman <Julian@GrayVines.com> | 2022-08-26 12:29:06 +0300 |
|---|---|---|
| committer | Julian Berman <Julian@GrayVines.com> | 2022-08-29 12:23:07 +0300 |
| commit | 3f7f1e34e359e290a2e636d111436d6c44d25930 (patch) | |
| tree | c5fc8dd9f96f1a60b361497cbe9badf01c55ece2 /docs | |
| parent | bde874d31c8aa2db5123f11ac919742ba7b1d741 (diff) | |
| download | jsonschema-3f7f1e34e359e290a2e636d111436d6c44d25930.tar.gz | |
And now yet again some new failures...
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/faq.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq.rst b/docs/faq.rst index ec34f71..51a7d2f 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -85,7 +85,7 @@ The JSON object ``{}`` is simply the Python `dict` ``{}``, and a JSON Schema lik The :kw:`$ref` keyword is a single notable exception. - Specifically, in the case where `jsonschema` is asked to `resolve a remote reference <RefResolver>`, it has no choice but to assume that the remote reference is serialized as JSON, and to deserialize it using the `json` module. + Specifically, in the case where `jsonschema` is asked to `resolve a remote reference <jsonschema.RefResolver>`, it has no choice but to assume that the remote reference is serialized as JSON, and to deserialize it using the `json` module. One cannot today therefore reference some remote piece of YAML and have it deserialized into Python objects by this library without doing some additional work. |