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

Fail to generate a proto with "routing" annotation #1090

Closed
summer-ji-eng opened this issue Jan 21, 2022 · 0 comments
Closed

Fail to generate a proto with "routing" annotation #1090

summer-ji-eng opened this issue Jan 21, 2022 · 0 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@summer-ji-eng
Copy link
Collaborator

summer-ji-eng commented Jan 21, 2022

Nodejs-bigtable fails on recently generating process. issue

Can't compile the generated code with a proto with new introduced google.api.routing annotation. proto

Generator is able to generate surface client library, but the generated client library fails on compiling.
Because to access the proto message property it require camelcase word than snakecase.

To reproduce the error, under the generator repo:

$ bazel build //...
$ bazel run //:gapic_generator_typescript --      --iam-service     --output-dir /tmp/bigtable2     -I "$GOOGLEAPIS"     --grpc-service-config "$GOOGLEAPIS/google/$APINAME/v2/${APINAME}_grpc_service_config.json"     --service-yaml "$GOOGLEAPIS/google/$APINAME/v2/${APINAME}_v2.yaml"      `find "$GOOGLEAPIS/google/$APINAME/v2" -name '*.proto'`     "$GOOGLEAPIS/google/cloud/common_resources.proto"
@summer-ji-eng summer-ji-eng added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

3 participants