golang-samber-oops

To add structured context to Go errors, use a fluent builder pattern with methods like In, With, User, and Tenant to attach domain attributes and stack traces. This ensures errors travel with rich context across HTTP handlers, services, and repositories.

Propagating error details through Go context is best achieved using WithBuilder and FromContext. This mechanism preserves builder attributes and traces as errors cross service boundaries, ensuring robust observability and low-cardinality error tracking during incident response.

You can convert Go panics into structured errors automatically by using the Recover function. This safely captures panics and transforms them into well-formed, machine-readable errors enriched with domain context and stack traces for debugging.

To separate public user-facing messages from technical traces in Go, use the Public and Code builder methods. Public sets a safe message for users, while Code and Wrapf attach machine-readable tags and technical context for backend observability.

Structured error handling works effectively for multi-layer Go applications by applying per-layer context enrichment. Handlers, services, and repositories can each append targeted attributes using Wrapf and With, producing robust traces without losing upstream context.