Hi,
I am trying to define an Openapi spec where I have the following paths:
- /{id}
- /lookups
When I perform a validation on the collection within the API Designer, I receive the following conflict.
The API Designer Collection validator does not understand a fixed path where there exists a path with a wildcard.
Definition used below that is causing issues:
/lookups:
get:
summary: Lookup Job Values
description: Lookup values for job fields
operationId: lookupJobValues
security:
- authorizer: []
parameters:
- in: path
name: include
schema:
type: string
required: true
description: Unique value to return list of possible job field values.
example: "cancellationReasons"
/{jobid}:
get:
summary: Get Job by ID
description: |
Retrieve a job by the identifier provided.
Query Parameters supported are:
* 'include' will return related entities to a Job. Can ask for 'quote' at this time.
operationId: getJobById
security:
- authorizer: []
parameters:
- in: path
name: jobid
schema:
type: string
required: true
description: Unique identifier for a job to retrieve.
example: "{{jobid}}"
- in: query
name: include
schema:
type: string
example: quote
required: false
description: Include related entities to a Job to be returned in request. Can ask for 'quote' at this time.
This appears to be allowed when looking at the Swagger Pet Store example.
https://petstore.swagger.io/
https://petstore.swagger.io/v2/swagger.json
"paths": {
"/pet/{petId}/uploadImage": {
"post": {}
},
"/pet": {
"post": {},
"put": {}
},
"/pet/findByStatus": {
}
...
}
Would someone be able to explain what I may be doing wrong?
Opened a bug in Github
Thank you!