Fix spec example: Plain text response with headers
Headers Object example from [Response Object Examples](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#response-object-examples) defines the type directly in the header element, but it should be inside a schema object - see [Headers Object Example](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#headers-object-example).
MODIFY
versions/3.0.md
versions/3.0.md
@@ -1732,18 +1732,24 @@ Plain text response with headers:
"headers": {
"X-Rate-Limit-Limit": {
"description": "The number of allowed requests in the current period",
+ "schema": {
"type": "integer"
+ }
},
"X-Rate-Limit-Remaining": {
"description": "The number of remaining requests in the current period",
+ "schema": {
"type": "integer"
+ }
},
"X-Rate-Limit-Reset": {
"description": "The number of seconds left in the current period",
+ "schema": {
"type": "integer"
}
}
}
+}
```
```yaml
@@ -1756,12 +1762,15 @@ content:
headers:
X-Rate-Limit-Limit:
description: The number of allowed requests in the current period
+ schema:
type: integer
X-Rate-Limit-Remaining:
description: The number of remaining requests in the current period
+ schema:
type: integer
X-Rate-Limit-Reset:
description: The number of seconds left in the current period
+ schema:
type: integer
```

Fix spec example: Plain text response with headers

Headers Object example from [Response Object Examples](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#response-object-examples) defines the type directly in the header element, but it should be inside a schema object - see [Headers Object Example](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#headers-object-example).