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 looking at the protoc-gen-json output of
protoc-gen-json
protoc -I. -Ivendor/github.com/grpc-ecosystem/grpc-gateway/third_party/googleapis/ --json_out=$(pwd)/out components/automate-gateway/api/iam/v2beta/policy.proto
run with this file, I see most of what I'd expect to see, but all the options fields a empty. For example,
options
"service": [ { "name": "Policies", "method": [ { "name": "CreatePolicy", "input_type": ".chef.automate.api.iam.v2beta.CreatePolicyReq", "output_type": ".chef.automate.api.iam.v2beta.CreatePolicyResp", "options": {} },
Am I missing something? Is there a way to have the options dumped as well? I do believe all the information should be in the CodeGenerationRequest 🤔
The text was updated successfully, but these errors were encountered:
Hah it's probably what was noted here:
If you wish to retain e.g. grpc-gateway google.api.http annotations, you'll need to make use of protoc-gen-dump instead of protoc-gen-json.
Sorry for the noise. 😄
Sorry, something went wrong.
At any rate, I'm still curious what an annotation needs to do to be json-encodable... Can you enlighten me? 😃
^^ cc @slimsag
No branches or pull requests
When looking at the
protoc-gen-json
output ofrun with this file, I see most of what I'd expect to see, but all the
options
fields a empty. For example,Am I missing something? Is there a way to have the options dumped as well? I do believe all the information should be in the CodeGenerationRequest 🤔
The text was updated successfully, but these errors were encountered: