Skip to content
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 OpenAPI/swagger documentation at run time? #138

Closed
tmc opened this issue Apr 18, 2016 · 4 comments
Closed

generate OpenAPI/swagger documentation at run time? #138

tmc opened this issue Apr 18, 2016 · 4 comments

Comments

@tmc
Copy link
Collaborator

tmc commented Apr 18, 2016

it'd be nice to easily serve up a live representation of the OpenAPI/swagger specification versus going to disk.

@joeblew99
Copy link

+1

This would be nice. I presume you mean the swagger-ui ?

@philips
Copy link

philips commented May 27, 2016

@joeblew99 @tmc You can just build it into the binary as I do in grpc-gateway-example: https://github.com/philips/grpc-gateway-example/blob/master/echopb/swagger.go

@tmc
Copy link
Collaborator Author

tmc commented May 27, 2016

@joeblew99 I meant the actual specs. It should be out of scope to include swagger-ui in this project.

@philips yeah, I go-rice my specs into the binary now but it's a bit janky.

@achew22
Copy link
Collaborator

achew22 commented Jan 4, 2017

@tmc This seems to me like it might be a problem better solved by your build system. I have implemented it myself using https://bazel.build. I assume that the //go:generate directive would allow you to achieve the same result but I have no real experience with it so I can't be sure.

I'm going to close this to try to get the bug list down to a single page but feel free to reopen if you have more thoughts on the topic.

@achew22 achew22 closed this as completed Jan 4, 2017
@tamalsaha tamalsaha mentioned this issue Mar 30, 2017
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants