You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+59-4Lines changed: 59 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
*[readOnly and writeOnly context](#readonly-and-writeonly-context)
17
17
*[Format validators](#format-validators)
18
18
*[Example](#example)
19
-
*[Resolution scopes](#resolution-scopes)
19
+
*[$ref resolution](#ref-resolution)
20
20
*[Javadoc](#javadoc)
21
21
22
22
<ahref="http://jetbrains.com"><imgsrc="./jetbrains-logo.png" /></a> Supported by JetBrains.
@@ -433,10 +433,10 @@ schema.validate(jsonDocument); // the document validation happens here
433
433
```
434
434
435
435
436
-
## Resolution scopes
436
+
## $ref resolution
437
437
438
438
In a JSON Schema document it is possible to use relative URIs to refer previously defined
439
-
types. Such references are expressed using the `"$ref"` and `"id"` keywords. While the specification describes resolution scope alteration and dereferencing in detail, it doesn't explain the expected behavior when the first occurring `"$ref"` or `"id"` is a relative URI.
439
+
types. Such references are expressed using the `"$ref"` and `"$id"` keywords. While the specification describes resolution scope alteration and dereferencing in detail, it doesn't explain the expected behavior when the first occurring `"$ref"` or `"$id"` is a relative URI.
440
440
441
441
In the case of this implementation it is possible to explicitly define an absolute URI serving as the base URI (resolution scope) using the appropriate builder method:
0 commit comments