-
Notifications
You must be signed in to change notification settings - Fork 127
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
Support $ref: {{model: Foo}} as in Swagger 2 plugin #19
Comments
Any news about this issue? Is there a plan to implement it? |
Also wondering about news on this feature. |
Does anyone know of a work-around for this? Currently we're deploying the service to amazon, then we're exporting the openapi doc from the deployed version. While this works it is very slow. Additionaly we use the openapi doc for generating the DTOs that our frontend needs. This workflow forces us to deploy the backend before we compile and test the front... |
This is now supported in a forked version https://www.npmjs.com/package/@martinsson/serverless-openapi-documentation There are some other additions too, fixing a bug where the requestModels property was ignored. |
Hi @martinsson would you accept any PR on your repo? |
Sure
…On Wed, May 4, 2022, 9:24 PM Gustavo Loera Vazquez ***@***.***> wrote:
Hi @martinsson <https://github.com/martinsson> would you accept any PR on
your repo?
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABMPQBTDKG56DFFEBIQNFLVILFG5ANCNFSM4EM2HJ7A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In Swagger 2 plugin I can reference models in other models. Most commonly, when an endpoint response model is an array containing item models. See the issue at the serverless-aws-documentation.
When I run
serverless openapi generate
on such configuration, I get this error:Feel free to close this issue if this is not going to be added soon, but I want something to refer to and to maybe have someone explain to me why I’m wrong. :-)
The text was updated successfully, but these errors were encountered: