-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
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
Operation parameter is $ref #621
Comments
+1 on this one |
I'm not sure why this is tagged as a feature and not as a bug. The spec says for a Operation Object parameters : The list can use the Reference Object to link to parameters that are defined at the Swagger Object's parameters. See also the related closed issues, swagger-api/swagger-editor#182 |
Because support for 2.0 is not yet officially released, and that's one of the features that need to be supported. |
+1 |
+1 really need this. since i have lots of common parameters, i use $ref frequently in operation object. |
we're getting there, please keep tracking this issue for the fix, which will be in swagger-ui-2.1.0-M2 |
For anyone that's still affected by this, I've made a simple tool that will work around this until it's resolved: https://github.com/duncanhall/expand-swagger-refs/ It takes a swagger schema as an input and outputs the same schema with $ref values manually expanded. |
👍 |
@duncanhall Thanks for the expand script. Gets me by just fine until it is added to master. |
addressed in 21d8a89 |
I have some parameters defined in the base swagger json object.
And I want to reference it in lots of operations as documented at https://github.com/wordnik/swagger-spec/blob/master/versions/2.0.md#operationObject
Here is my fix in swagger-client.js
At line 428 I added
And to be able to point to parent.parameters I added at line 280
The text was updated successfully, but these errors were encountered: