Sure, but if people are working on a concerted effort to support google.rpc.Status <https://cloud.google.com/apis/design/errors#error_model> in a bunch of grpc language libraries (Java, Go, grpc-web/JS, ...) so that developers building grpc apps with those languages can use it for richer error reporting, this effort should be publicized so that developers can take advantage of it when appropriate.
If it's good enough for Google Cloud to standardize on, why shouldn't it be documented for others to standardize on? On Wednesday, May 22, 2019 at 11:26:23 AM UTC-7, Penn (Dapeng) Zhang wrote: > > The grpc core library io.grpc:grpc-core > <https://www.google.com/url?q=https%3A%2F%2Fsearch.maven.org%2Fsearch%3Fq%3Da%3Agrpc-core&sa=D&sntz=1&usg=AFQjCNH6o5Hz1JqFnqPZvL66Pp3LqXtu0A> > does > not and should not depend on protobuf, so we can not use google.rpc.Status > <https://cloud.google.com/apis/design/errors#error_model> as a > replacement of io.grpc.Status > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgrpc%2Fgrpc%2Fblob%2Fmaster%2Fsrc%2Fproto%2Fgrpc%2Fstatus%2Fstatus.proto&sa=D&sntz=1&usg=AFQjCNGETk39EM57QWTtCtv7Z77kVWCxPA> > at > the core library level. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/7ddab0d4-fb6f-40d9-8e96-6f1abc8bb2fa%40googlegroups.com.
