go-error-mapper

Generate a typed domain error package for Go that translates specific business logic failures into appropriate gRPC status codes like NotFound or InvalidArgument, ensuring clients can handle distinct error scenarios gracefully instead of receiving generic Internal errors.

Yes, you can map Go domain errors to HTTP status codes. The generated typed error package optionally supports mapping domain-specific errors to corresponding HTTP status codes for RESTful APIs alongside the primary gRPC status code mapping.

Go microservices return generic codes.Internal because developers often lack a standardized error mapping mechanism. Defining typed domain errors and specifying target transports allows automatic mapping to correct gRPC status codes based on the specific business logic failure.

Generate a Go error handling package with stack trace capture by defining custom typed domain errors and specifying your target transports. The generated package includes optional stack trace capture to enhance debugging capabilities for gRPC and HTTP services.

Before generating a Go domain error package, you need to define your custom domain error types representing specific business logic failures and specify the target transports, such as gRPC and HTTP, for accurate status code mapping generation.