Extend content and spec #3
Conversation
I think headers likely appear more in response descriptions than in any other objects.
Add headers example text
WIP Add to OpenAPI document, add validation, some writing
…erve as reference.
There is a `name` field in the `http` auth type, so I'd rather avoid ambiguity here.
Security scheme edit
Add composition
openapi.yaml Outdated
| - prod | ||
| - staging | ||
| - dev | ||
| # TODO: Wat for OAS3.1 bug fix - Variables in server URLs are not currently supported. |
There was a problem hiding this comment.
This looks to be have merged now, would be interested in know what issue you ran into as we use variables successfully in our validator and generator atm
There was a problem hiding this comment.
@TristanSpeakEasy - great, should be released soon then I think. Here's what Niel said about it.
I commented out sections that failed strict validation, but will restore this one because the spec will allow for this soon and most libraries should already validate against the future version.
While working on the example schema, I used a strict validator to make sure we don't break things while adding operations etc. The released (JSON/YAML) version of OpenAPI 3.1 still forces valid URLs in Server Objects, but I'm sure they'll release an update soon. Speakeasy's validator correctly interprets the markdown spec here (which is the source of truth, after all), so this was not a Speakeasy problem. We'll uncomment this and update our validator.
Proposal language edit
Readme language edit
Ritza/complete first draft
No description provided.