[Question] improved errors in production project

[solarhell]

Is there anything like this in connect-rpc world?

Currently only grpc defined error can be returned in connectrpc.

Clients need to use string compare to match the underlying error.

[timostamm]

The Connect protocol is designed so that it can be transcoded to and from the gRPC protocol. This means that we are limited to the error codes also present in gRPC.

However, Connect (and most gRPC implementations) support error details. You can arbitrary Protobuf messages to provide error details. You can find documentation here, and they are also covered in the protocol spec.

[solarhell]

Yeah, maybe I'll use proto to define errors and embed them as generic responses to zig-zag my way to custom errors, cause error matching for string comparison doesn't work well.