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
@@ -935,7 +935,7 @@ The following table shows serialized examples, as would be shown with the `seria
935
935
936
936
#### Extending Support for Querystring Formats
937
937
938
-
Many frameworks define query string syntax for complex values, such as appending array indices to parameter names or indicating multiple levels of of nested objects, which go well beyond the capabilities of the `deepObject` style.
938
+
Many frameworks define query string syntax for complex values, such as appending array indices to parameter names or indicating multiple levels of nested objects, which go well beyond the capabilities of the `deepObject` style.
939
939
940
940
As these are not standards, and often contradict each other, the OAS does not attempt to support them directly.
941
941
Two avenues are available for supporting such formats with `in: "querystring"`:
@@ -1070,7 +1070,7 @@ examples:
1070
1070
dataValue:
1071
1071
page: 4
1072
1072
pageSize: 50
1073
-
serializeValue: page=4&pageSize=50
1073
+
serializedValue: page=4&pageSize=50
1074
1074
```
1075
1075
1076
1076
A complex parameter using `content` to define serialization, with multiple levels and types of examples shown to make the example usage options clear — note that `dataValue` is the same at both levels and does not need to be shown in both places in normal usage, but `serializedValue` is different:
@@ -2383,7 +2383,7 @@ The `serializedValue` and `externalValue` fields both MUST show the serialized f
2383
2383
For Media Type Objects, this is a document of the appropriate media type, with any Encoding Object effects applied.
2384
2384
For Parameter and Header Objects using `schema` and `style` rather than a Media Type Object, see [Style Examples](#style-examples) for what constitutes a serialized value.
2385
2385
2386
-
##### Criteria for `serializedExample`
2386
+
##### Criteria for `serializedValue`
2387
2387
2388
2388
A serialization can be represented as a valid Unicode string in `serializedValue` if any of the following are true of the serialization:
2389
2389
@@ -2858,7 +2858,7 @@ components:
2858
2858
In an HTTP message, the serialized example would look like:
2859
2859
2860
2860
```http
2861
-
Set-Cookie: lang=en-US; Expires=Wed, 09 Jun 2021 10:18:14 GM
2861
+
Set-Cookie: lang=en-US; Expires=Wed, 09 Jun 2021 10:18:14 GMT
2862
2862
Set-Cookie: foo=bar; Expires=Wed, 09 Jun 2021 10:18:14 GMT
0 commit comments