Replies: 1 comment
-
|
Hey Evan, once you have the base64-decoded data from the protobuf-ts uses @grpc/grpc-js under the hood for gRPC, and it doesn't offer any support for error details, unfortunately. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Google has a rich error handling model which supports embedding custom error details in RpcError metadata: https://grpc.io/docs/guides/error/#richer-error-model.
Any there currently any plans to support this as part of Protobuf-ts?
I've been able to verify that the error details are available by base64 decoding the included metadata field for "grpc-status-details-bin" using a custom RPC interceptor, so it appears to be possible to unpack err details on the client side
Beta Was this translation helpful? Give feedback.
All reactions