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
It currently isn't possible to fully take advantage of and interact with (and produce) gRPC services that make use of the full RPC Error Model because the GrpcError class is missing the details field as defined in google/rpc/status.proto.
One example use case out of many is being able to access retry_delay for behaving nicely with a service.
This would help developers avoid baking in custom error details into their custom response message definitions themselves. My current workaround for Dart (and the other languages that don't support this yet) is to encode google.rpc.Status into (a JSON String field in) the message field.
The text was updated successfully, but these errors were encountered:
It currently isn't possible to fully take advantage of and interact with (and produce) gRPC services that make use of the full RPC Error Model because the
GrpcError
class is missing thedetails
field as defined ingoogle/rpc/status.proto
.One example use case out of many is being able to access
retry_delay
for behaving nicely with a service.This would help developers avoid baking in custom error details into their custom response message definitions themselves. My current workaround for Dart (and the other languages that don't support this yet) is to encode
google.rpc.Status
into (a JSON String field in) themessage
field.The text was updated successfully, but these errors were encountered: