There are many scenarios when application would want to see custom error
codes even if just for logging/better visibility. The pattern I use:
1. Stick a google::rpc::status in every response message.
2. Create a Message with embedded enums next to the Service definition in
the proto file. Each
Responses inline
On Thursday, April 12, 2018 at 2:52:10 PM UTC-7, Ruslan Nigmatullin wrote:
>
> Hi,
>
> Is there a chance to add details to errors generated by gRPC layer itself
> to distinguish different scenarios instead of forcing gRPC users to analyze
> error message client-side? Parsing
The problem with that is there is not a fine-grained set of codes that we
can support. Particularly, the server application may return status codes
with their own definition. Adding codes is not likely to help with the
situation for gRPC since there would always be scenarios that is not
