Way to access the string description of error from RPC method about grpc-go

[maxhawkins]

+1

Exposing these fields would also give errors a better JSON serialization, which could be useful when mapping GRPC to a REST API.

[yinhm]

+1

I want to return something like "404 page not found" to the client, It would be easier if export RPCError.

[iamqizhao]

We did not construct a new exported type for RPC error because we were
discussing whether we should open source the google internal status type
which has been used by all rpc frameworks and a lot of others inside google
and rpcErr was treated as a short-to-medium term solution. But that
discussion went silent for a while... I will see how I can rpcErr itself
better probably sometime next week and try to revive the previous
discussion. Thanks for all the valuable suggestions here!

On Sat, Mar 28, 2015 at 11:59 AM, yinhm [email protected] wrote:

+1

I want to return something like "404 page not found" to the client, It
would be easier if export RPCError.

—
Reply to this email directly or view it on GitHub
#110 (comment).

[maxhawkins]

Could you make rpcErr similar enough to the internal status type that it will be compatible when/if you open source it? In the meantime a decent JSON serialization would be tremendously helpful.

[hezhit]

+1
rpcErr is very useful for error handling.

[joeatwork]

+1
It'd be great to be able to pass and read error descriptions

[sym3tri]

This is something I am very much in need of. Otherwise we'll have to resort to the gross last resort of parsing the error string.

[iamqizhao]

How about adding a Desc(err error) string to return the original error
description?

On Tue, Sep 22, 2015 at 2:50 PM, Ed Rooth [email protected] wrote:

This is something I am very much in need of. Otherwise we'll have to
resort to the gross last resort of parsing the error string.

—
Reply to this email directly or view it on GitHub
#110 (comment).

[sym3tri]

@iamqizhao that would suite my needs and seems like a very simple solution.