Skip to content

Commit 4435fd3

Browse files
committed
Fix more example bugs
Never change your directory structure halfway through writing examples...
1 parent 2832652 commit 4435fd3

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
@@ -5215,7 +5215,7 @@ paths:
52155215
/foo:
52165216
get:
52175217
requestBody:
5218-
$ref: "shared#/components/requestBodies/Foo"
5218+
$ref: "shared/foo#/components/requestBodies/Foo"
52195219
```
52205220

52215221
Assume the retrieval URI for the following document is `https://git.example.com/shared/blob/main/shared/foo.yaml`:
@@ -5249,7 +5249,7 @@ In this example, the retrieval URIs are irrelevant because both documents define
52495249
For the relative `$ref` in the first document, it is resolved against `$self` to produce `https://example.com/shared/foo#/components/requestBodies/Foo`.
52505250
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.
52515251

5252-
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`.
5252+
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`.
52535253
This matches the `$id` at `#/components/schemas/Foo/$id` so it points to that Schema Object.
52545254
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`.
52555255

0 commit comments

Comments
 (0)