oops
oops copied to clipboard
samber
🔥 Error handling library with context, assertion, stack trace and source fragments
It would be helpful to embed source code in binary, since the `.Sources()` getter read the sources at runtime, at location specified in the stack trace. I don't see any...
Current stacktrace just append strings, which is not good to read. Can oops have some structured stacktrace implementation like https://github.com/rotisserie/eris ? ``` "root":{ "message":"error internal server", "stack":[ "main.main:/Users/roti/go/src/github.com/rotisserie/eris/examples/logging/example.go:143", "main.ProcessResource:/Users/roti/go/src/github.com/rotisserie/eris/examples/logging/example.go:85", "main.ProcessResource:/Users/roti/go/src/github.com/rotisserie/eris/examples/logging/example.go:82",...
Hi @samber, I tried using oops with zap here is my example: ```go func main() { logger, _ := zap.NewProduction() err := oops. In("repository"). Tags("database", "sql"). With("deneme", "mehmet"). Errorf("could not...
Both Recover and Recoverf helpers should build stack traces using `debug.Stack()` in order to print trace up to the panic line.
Currently, the `.Format()` exporter does not return colorized output. I wonder if we should automatically detect a tty mode or add a global parameter. I'm not even sure this is...
I added support for Trace and Span which are ULID by default. For now, Span are not exported from `ToMap()`, `Format()`, `Marshal()` and `LogValuer`. Is this expected and how should...