golang-error-handling

To wrap Go errors with context, use the %w verb when returning errors to preserve the original chain. This allows errors.Is and errors.As to inspect the root cause while logging the added context via slog.

Avoid duplicate error logs in Go by applying the single handling rule, which ensures errors are logged only once at the boundary layer to produce clear user-facing messages without redundant entries.

errors.Join composes Go error chains by combining multiple errors into a single value. This allows errors.Is and errors.As to inspect all joined errors simultaneously during propagation and testing.

Yes, slog supports structured logging of Go errors by pairing context-rich logs with wrapped errors. This promotes consistent observability and satisfies production error tracking requirements.

samber/oops works with standard Go error wrapping by extending %w and errors.Is patterns. It provides structured logging capabilities that integrate with idiomatic error chains for enhanced observability.

Use errors.As in Go when you need to access a specific typed error's fields, whereas errors.Is only checks if an error matches a sentinel value. Both inspect wrapped error chains effectively.