feat: Add Zap logger formatter with an example. #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
feat: Add Zap logger integration
Description
This PR introduces official support for the Zap logging library, allowing oops.OopsError to be logged with structured context and stack traces using Zap's high-performance field system.
Changes:
Implemented loggers/zap package with OopsMarshalFunc and OopsStackMarshaller.
Added comprehensive unit tests and benchmarks for the Zap formatter.
Added a full usage example in examples/zap.
Updated go.work to include the new modules.
Fixed a brittle test in stacktrace_test.go that failed when the build path didn't contain the module name.