We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example Swagger/OpenAPI definition:
openapi: 3.0.3 info: title: Parameters example version: 1.0.0 servers: - url: 'https://127.0.0.1/api/rest' paths: '/foo/{bar}': post: parameters: - name: bar in: header schema: type: string requestBody: content: application/json: schema: type: string responses: '200': description: Example content: application/json: schema: type: string delete: responses: '200': description: OK parameters: - required: true name: bar in: path schema: type: string
Swagger-UI configuration options:
SwaggerUI({ // your config options here })
?yourQueryStringConfig
Specification says A unique parameter is defined by a combination of a name and location.
A unique parameter is defined by a combination of a name and location.
I defined bar parameter in path location at PathItem and I defined parameter with same name bar, in header location at Operation.
bar
PathItem
Operation
Steps to reproduce the behavior:
Expected two parameters in POST method: bar in path location and foo in header location.
foo
Related question in OpenAPI-Specification repo.
OpenAPI-Specification
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Swagger-UI configuration options:
Describe the bug you're encountering
Specification says
A unique parameter is defined by a combination of a name and location.
I defined
bar
parameter in path location atPathItem
and I defined parameter with same namebar
, in header location atOperation
.To reproduce...
Steps to reproduce the behavior:
bar
in header location displayed. Nobar
in path location parameter.Expected behavior
Expected two parameters in POST method:
bar
in path location andfoo
in header location.Screenshots
Additional context or thoughts
Related question in
OpenAPI-Specification
repo.The text was updated successfully, but these errors were encountered: