golang-samber-oops

Structured Go error handling with samber/oops lets you wrap errors using a fluent builder chain with .In(), .Tags(), and .Code() methods, attaching domain context, stack traces, and attributes for better observability.

The best way to separate public and technical messages in Go is using samber/oops, which provides .Public() for user-safe messages while keeping technical details and stack traces internal for logging and debugging.

You can recover from panics and convert them to structured errors in Go by applying samber/oops .Recover() or .Recoverf() methods, which capture the panic and wrap it with stack traces and contextual attributes.

Yes, you can propagate error builders through context in Go applications by storing and retrieving samber/oops builders using oops.WithBuilder and oops.FromContext, allowing context-rich error wrapping across HTTP handlers and service layers.

Structured error handling in Go integrates seamlessly with slog, zerolog, and logrus, allowing you to attach error data like codes, tags, and stack traces directly to your structured logging output for improved observability.

Yes, you need the Go toolchain and the samber/oops package installed in your Go codebase to build and wrap errors with attributes, stack traces, and public messages across your application layers.