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: src/oas.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -270,7 +270,7 @@ Unless specified otherwise, relative references are resolved using the URLs defi
270
270
271
271
Assume a retrieval URI of `https://device1.example.com` for the following OpenAPI Document:
272
272
273
-
```YAML
273
+
```yaml
274
274
openapi: 3.2.0
275
275
$self: https://apidescriptions.example.com/foo
276
276
info:
@@ -5353,7 +5353,7 @@ For OpenAPI Documents, this source is the OpenAPI Object's `$self` field, while
5353
5353
5354
5354
Assume the retrieval URI of the following document is `file://home/someone/src/api/openapi.yaml`:
5355
5355
5356
-
```YAML
5356
+
```yaml
5357
5357
openapi: 3.2.0
5358
5358
$self: https://example.com/api/openapi
5359
5359
info:
@@ -5368,7 +5368,7 @@ paths:
5368
5368
5369
5369
Assume the retrieval URI for the following document is `https://git.example.com/shared/blob/main/shared/foo.yaml`:
5370
5370
5371
-
```YAML
5371
+
```yaml
5372
5372
openapi: 3.2.0
5373
5373
$self: https://example.com/api/shared/foo
5374
5374
info:
@@ -5416,7 +5416,7 @@ Note that this is purely an example, and support for such multipart documents or
5416
5416
5417
5417
RFC2557 was written to allow sending hyperlinked sets of documents as email attachments, in which case there would not be a retrieval URI for the multipart attachment (although the format could also be used in HTTP as well).
0 commit comments