Skip to content

Commit 837a30b

Browse files
committed
Fix more example bugs
Never change your directory structure halfway through writing examples...
1 parent 71b9436 commit 837a30b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/oas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4949,7 +4949,7 @@ paths:
49494949
/foo:
49504950
get:
49514951
requestBody:
4952-
$ref: "shared#/components/requestBodies/Foo"
4952+
$ref: "shared/foo#/components/requestBodies/Foo"
49534953
```
49544954

49554955
Assume the retrieval URI for the following document is `https://git.example.com/shared/blob/main/shared/foo.yaml`:
@@ -4983,7 +4983,7 @@ In this example, the retrieval URIs are irrelevant because both documents define
49834983
For the relative `$ref` in the first document, it is resolved against `$self` to produce `https://example.com/shared/foo#/components/requestBodies/Foo`.
49844984
The portion of that URI before the '#' matches the `$self` of the second document, so the reference target is resolved to `#/components/requestBodies/Foo` in that second document.
49854985

4986-
In that document, the `$ref` in the Request Body Object is resolved using that document's `$self` as the base URI, producing `https://example.com/schemas/foo`.
4986+
In that document, the `$ref` in the Request Body Object is resolved using that document's `$self` as the base URI, producing `https://example.com/api/schemas/foo`.
49874987
This matches the `$id` at `#/components/schemas/Foo/$id` so it points to that Schema Object.
49884988
That Schema Object has a subschema with `$ref: bar`, which is resolved against the `$id` to produce `https://example.com/schemas/bar`, which matches the `$id` at `#/components/schemas/Bar/$id`.
49894989

0 commit comments

Comments
 (0)