We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When defining repeated fields the documentation of the field is overwritten by the fields comments. For example:
// Some field comments repeated string names = 2 [(grpc.gateway.protoc_gen_swagger.options.openapiv2_field) = { description: "Some field description documentation." array: ["name1", "name2"]; }];
After generating the swagger documentation the field comments takes precendence over the field documentation resulting in something like:
{ "name": "names", "description": "Some field comments", "in": "query", "required": false, "type": "array", "items": { "type": "string" } }
I think that the field documentation must take precedence over the field comments.
The text was updated successfully, but these errors were encountered:
This would be a really great starter project for getting involved!
This comes from the interaction of these two pieces of code.
grpc-gateway/protoc-gen-swagger/genswagger/template.go
Lines 120 to 124 in c3923b1
Lines 294 to 296 in c3923b1
A little bit of rejiggering in there + a new test case and I think you'd be done if you're interested.
Sorry, something went wrong.
Sure, I will definitely try, thank you for taking me in the right direction!
Closed by #863
No branches or pull requests
Bug report:
When defining repeated fields the documentation of the field is overwritten by the fields comments. For example:
After generating the swagger documentation the field comments takes precendence over the field documentation resulting in something like:
I think that the field documentation must take precedence over the field comments.
The text was updated successfully, but these errors were encountered: