error-handling

Handle multiple Go errors by using errors.Join to aggregate failures into a single error, preserving all underlying causes. This pattern is ideal for aggregating results from several calls while maintaining rich context across microservices and CLI tools.

The best way to wrap Go errors is using fmt.Errorf with multiple %w verbs to retain rich context across layers. This preserves the error chain, allowing callers to unwrap and inspect underlying causes robustly.

errors.Is and errors.As work by traversing the error chain created by %w wrapping or errors.Join. They robustly check if a specific error or error type exists in the chain, ensuring accurate error matching across layers.

Yes, you can integrate Go error handling with slog for structured logging. Aligning error propagation with slog-friendly logging preserves error chains and debuggability, ensuring consistent observability across microservices.

Yes, this approach applies to Go 1.20+ projects. It enforces usage of errors.Join and multiple %w wrapping, which are features available in these versions, ensuring robust error reporting and clean propagation in libraries and microservices.

Use errors.Join when aggregating results from several calls into a single error to preserve all failure causes. Use fmt.Errorf with %w when you need to add contextual information to a single error across different layers.