-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
protoc_gen_swagger should use target_name.swagger.json as out #640
Comments
It's an important feature. I can't find a third-party tool to solve this unless parsing swagger.json files by myself. |
Well, I'll take a look at it this weekend. It seems make it work by just adding some test cases. |
Yep, that's exactly what we need to get it submitted 😄 |
Combine separate swagger file to one in #643 |
p2p: add handshake
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
By default protoc_gen_swagger should use target_name.swagger.json as the output file and use something like #591 to generate a single file output of that name.
The text was updated successfully, but these errors were encountered: