-
Notifications
You must be signed in to change notification settings - Fork 372
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
Generate swagger spec from source #20
Comments
I started doing this task by using go-swagger and this is not so easy how it was seamed. But I`ve done some work and have a question. @awalias @kiwicopple Do I need include description of /admin/* , /saml/* , /instances/* to result ? Because in README that groups aren't been covered |
Ideally it will autogen everything - is there some manual work to enable the routes? |
Every route need to be described manually and then spec will be generated according to it |
I see, perhaps we start with a very small set of routes and then expand it if it seems like it's the right long-term solution? |
Yeah, I agree. Initial set of routes will be the same as in REAMDE. I think that it's enough to start |
Hey! Thanks for looking into the issue! Unfortunately, the Swagger spec has been de-prioritized for the moment as we don't quite have the bandwidth to maintain it. I'm going to close this for now but feel free to re-open if you have any questions or concerns. Thanks! |
https://medium.com/@pedram.esmaeeli/generate-swagger-specification-from-go-source-code-648615f7b9d9
The text was updated successfully, but these errors were encountered: