OpenAPI-Specification

OpenAPI-Specification copied to clipboard

Inconsistency in runtime expression examples for request headers

2

[Runtime expression examples](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#examples-1) include the following: Source Location | example expression | notes ---|:---|:---| Requested media type | `$request.header.accept` | Request parameter | `$request.path.id` | Request parameters MUST be declared...

hkosova

Path Templating with multiple parameters allows for ambiguous parsing

4

Currently the support for path segments is ambiguous even in simple cases: Consider: ``` paths: /{foo}:{bar}/update: post: summary: Example API with multiple parameters parameters: - name: foo in: path description:...

richardwhiuk

Given the growing number of examples in the specification, it would be nice to (semi-)automatically create „pass“ test cases from Markdown spec text. This would help keeping the examples correct...

ralfhandl

I expected it would (e.g. `contentType: text/css, text/javascript, image/*`) by analogy with the `Accept` header, while @ralfhandl read it more literally and expects only `contentType: text/css,text/javascript,image/*` would be allowed. I...

handrews

Auth URL Variables

2

Currently we can set the server variables for different environments like so: ```(yaml) servers: - url: 'https://{environment}.example.com/v1' variables: environment: default: api enum: - api - sandbox.api - development.api - staging.api...

michaelmerrill

Clarification on JWT Bearer access token from OAuth2 Client Credentials Grant...

2

Hello, First time building a spec with OpenAPI and appreciate the thoughtfulness of this spec. The changes in OpenAPI3 are really nice. I'm lost on one point: The endpoints will...

cadethacker