golang-error-handling

Wrap Go errors using fmt.Errorf with the %w verb to preserve the original error chain, then inspect the hierarchy with errors.Is or errors.As to match sentinel values and extract structured types for robust error propagation.

Structured logging of Go errors across layered services is handled using slog and samber/oops to attach contextual attributes, enabling central error handling and HTTP request logging middleware to trace error propagation through layers.

Combine multiple Go errors using errors.Join to aggregate failures into a single error value, allowing you to inspect individual wrapped errors with errors.Is and log the collected context via slog for observable debugging.

Yes, samber/oops integrates with slog for idiomatic Go error handling by wrapping errors with contextual attributes that slog consumes, allowing production errors to carry traceable context through HTTP request logging middleware.

Create sentinel error types in Go using stable error messages and var declarations, then match them throughout your service layers using errors.Is to ensure consistent error inspection and propagation across handlers and middleware.

Use panic and recover for Go error handling only for truly unrecoverable program states, not routine control flow; idiomatic Go error handling requires returning wrapped errors with fmt.Errorf and propagating them through service layers.