gapic-generator-ruby
gapic-generator-ruby copied to clipboard
Generate Ruby gRPC client libraries from Protocol Buffer definitions.
This appears in `google-cloud-firestore-admin-v1/proto_docs/google/firestore/admin/v1/location.rb` It is currently converting `[google.cloud.location.Location.metadata][google.cloud.location.Location.metadata]` to `{::Google::Cloud::Location::Location#metadata google.cloud.location.Location.metadata}`, but the class is defined in a dependency (google-cloud-location); hence YARD tests fail. (We are currently working around...
This is brought on by https://github.com/googleapis/google-cloud-ruby/issues/14050 The end-user does not know about the default per-rpc timeout being generated, so they just percieve the client-wide timeout to 'not have any effect'....
Currently the underlying `GRPC::ActiveCall::Operation` is exposed to users directly for every method call and it is the only way to access some gRPC properties, like the `trailing_metadata`. This could be...
The [google-cloud-pubsub](https://github.com/googleapis/google-cloud-ruby/blob/master/google-cloud-pubsub) library is required to support the following RPC retry policy, provided by the Pub/Sub team: | property | default value | | ---------------------- | ------ | | init...
Include `ruby-cloud-generate-standalone-snippets` and `ruby-cloud-generate-yardoc-snippets` in `shared/test_resources/api_test_resources.rb`, and in fact we should probably turn them on for all tests and embedded outputs at this point. Note this may depend on #629.
Rework the unit tests for diregapic so that the test harness does not duplicate helper methods from gapic-common/rest
https://github.com/googleads/google-ads-ruby/issues/246 for details. The question is whether error wrapping is working as intended.
TLDR: we would like to have the conversion of `GRPC::BadStatus` errors to `Google::Cloud::Error`s in the `Enumerable` result of streaming calls of the spanner client, so that the consumer only has...
Protos allow some fields to be connected in what essentially are the oneof groups. Assigning one field in the group will essentially prevent others from being assigned and there might...
Currently IIRC the logic is 'every argument except the last' or something close but should take segment ids with/without patterns into an account