golang-error-handling

Idiomatic Go error handling with slog uses structured logging to capture rich context. You wrap errors with %w and log them at system boundaries using %v, enforcing a single handling rule to either log or return.

The best way to wrap Go errors is using %w to add context. Use errors.Is to check for specific sentinel values and errors.As to extract custom error types, ensuring safe inspection across all application layers.

You can combine independent Go errors using errors.Join. This function aggregates multiple errors into a single error value, which is useful when collecting validation failures or concurrent operation errors.

Yes, samber/oops integrates with Go middleware for HTTP request logging. It enforces consistent middleware patterns by applying structured logging and the single handling rule to log versus return errors across HTTP boundaries.

Use %w for Go error wrapping to maintain the error chain for inspection via errors.Is and errors.As. Use %v at system boundaries to format the error as a string when returning to external clients.