You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
generate a using statement for the gax::Operation response in the client and use it in the generated method. E.g.:
using GetBigFooOperation = gax::Operation<Foo, FooMeta>;
This turns this code:
gax::StatusOr<gax::Operation<Foo, FooMeta>> res = client.GetBigFoo(getBigFooRequest);
if (res) {
gax::Operation<Foo, FooMeta> op = *std::move(res);
}
into this:
gax::StatusOr<GetBigFooOperation> res = client.GetBigFoo(getBigFooRequest);
if (res) {
GetBigFooOperation op = *std::move(res);
}
This is not only a saving of characters typed, but also ties together the two parameters (result and metadata type) into a single type that describes a particular operation. These parameters and not mix-and-matchable, so it makes sense to treat each possible LRO response as a unit.
The text was updated successfully, but these errors were encountered:
For each LRO rpc e.g.
generate a
using
statement for the gax::Operation response in the client and use it in the generated method. E.g.:using GetBigFooOperation = gax::Operation<Foo, FooMeta>;
This turns this code:
into this:
This is not only a saving of characters typed, but also ties together the two parameters (result and metadata type) into a single type that describes a particular operation. These parameters and not mix-and-matchable, so it makes sense to treat each possible LRO response as a unit.
The text was updated successfully, but these errors were encountered: