Does OpenAPI 3.0 supports enum as reusable component for Path Parameters?

Question

Hi There,&nbsp;&nbsp;Does OpenAPI 3.0 supports enum as reusable component for Path Parameters?Here is an example"parameters:- in: path&nbsp;name: status&nbsp;schema:&nbsp; &nbsp; &nbsp;type: string&nbsp; &nbsp; &nbsp;$ref: "#/components/schemas/Status"&nbsp;Status:&nbsp; &nbsp; type: string&nbsp; &nbsp; enum:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Approved&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Pending&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Closed&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Newis it valid syntax?

ponelat · Answer

Hi&nbsp;ssingh137&nbsp;,
&nbsp;
Yes it's possible to reuse schemas in Parameters.
&nbsp;
See an example here:&nbsp;https://app.swaggerhub.com/apis/SwaggerPMTests/reuseable-enum/1.0.0#/default/get_foo__bar_
&nbsp;
For more info around Path Parameters, see:&nbsp;https://swagger.io/docs/specification/describing-parameters/#path-parameters
&nbsp;
Note: You cannot have sibling fields next to a $ref. In your example you have `type: string` next to a `$ref: ...` and that is invalid.&nbsp;

Forum Discussion

Does OpenAPI 3.0 supports enum as reusable component for Path Parameters?

1 Reply

Related Content

Reference parameters/components from another OpenAPI json (same project)

Support "allowReserved" for path parameters

Browser component disabled.

Browser component is disabled

soapui parameter equivalent to curl parameter

Recent Discussions

Issue with INT ENUM types while generating for python

convert our OpenAPI 2.0 swagger files to OpenAPI 3.0 on-premises

Exploring Tax-saving Options: SBI Long Term Equity Fund vs. Parag Parikh Tax Saver Fund

OpenApi enum with multiple values

Multiple urls for tokenUrl for multiple servers