-
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
Generate Swagger documentation #469
Comments
Good news! With @ivucica's recent PR being submitted we now support adding additional fields in the OpenAPIv2 spec. If there are more fields that you need than are available in the example proto then please reopen this bug and we can discuss. |
Either I am doing something wrong or it is not generating proper swagger specs. My proto file:
My Makefile:
Generated swagger spec:
Swagger does not have required fields or title. |
I think it does. See: https://github.com/OAI/OpenAPI-Specification/blob/fb059ca461bd17b10a9e3e59879f04485886d356/versions/2.0.md Search for Not that Pasting your generated JSON into https://editor.swagger.io also throws no errors. Why do you believe |
Oh, you mean the I've added many fields to the schema without adding support for outputting them. I'm sure PRs will be accepted. You'll want to update |
@ivucica Okay, got it. Thank you for your quick response :) |
Can protoc-gen-swagger parse proto3 syntax? |
1. This is not a support channel. :-)
2. gRPC is primarily proto3.
3. protoc-gen-swagger is a plugin for protoc, so it doesn’t parse proto files directly. Therefore, yes.
26.12.2017., u 11:09, korisnik Public Repository of A.Minchekov <[email protected]> je napisao:
… Can protoc-gen-swagger parse proto3 syntax?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hello,
Is there anyway to fill swagger documentation fields ?
For example: required, format, min_length, etc.
In structs we can do it via comments:
How can I reach this documenting my proto files ?
The text was updated successfully, but these errors were encountered: