We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
assume schema has this paths:
/store
/store/{store_id}
/store/{store_id}/offers
/store/{store_id}/offers/{offer_id}
and the {store_id} and {offer_id} are id's that are generated in the same manner (e.g. string($uuid))
{store_id}
{offer_id}
string($uuid)
it would be beneficial if pathId schema could be defined in the components/parameters
pathId
components/parameters
"parameters": { "pathId": { "name": "id", "in": "path", "required": true, "schema": { "type": "string", "format": "uuid" }, "example": "3fa85f64-5717-4562-b3fc-2c963f66afa6" } }
and then later reused for the parameter definition in the paths section
parameter
paths
The text was updated successfully, but these errors were encountered:
Related (or duplicate of): #2026
Sorry, something went wrong.
Duplicate of #2026
thanks @hkosova this is subset of the mentioned issue
sibling to #2498
No branches or pull requests
assume schema has this paths:
/store
/store/{store_id}
/store/{store_id}/offers
/store/{store_id}/offers/{offer_id}
and the
{store_id}
and{offer_id}
are id's that are generated in the same manner (e.g.string($uuid)
)it would be beneficial if
pathId
schema could be defined in thecomponents/parameters
and then later reused for the
parameter
definition in thepaths
sectionThe text was updated successfully, but these errors were encountered: