MapObjectEncoder.AppendByteStringnot adding value as a string.
zap.Optionfor creating test loggers.
Thanks to @iaroslav-ciupin, @lelenanam, @joa, @NWilson for their contributions to this release.
Thanks to @nfarah86, @AlekSi, @JeanMertz, @philippgille, @etsangsplk, and @dimroc for their contributions to this release.
zapcore.Fieldto clean up GoDoc.
Thanks to @DiSiqueira and @djui for their contributions to this release.
NewStdLogAt, which extends
NewStdLogby allowing the user to specify the level of the logged messages.
ContextMapmethod to observer logs for simpler field validation in tests.
Thanks to @richard-tunein and @pavius for their contributions to this release.
This release fixes two bugs.
This release adds a few small features and is fully backward-compatible.
EncoderConfig, allowing users to override the Unix-style default.
fmt.Stringer, which makes a variety of operations a bit simpler.
This release adds an enhancement to zap's testing helpers as well as the ability to marshal an AtomicLevel. It is fully backward-compatible.
This release adds a gRPC compatibility wrapper. It is fully backward-compatible.
zapgrpcpackage that wraps zap's Logger and implements
This release fixes two bugs and adds some enhancements to zap's testing helpers. It is fully backward-compatible.
Thanks to @moitias for contributing to this release.
This is zap's first stable release. All exported APIs are now final, and no further breaking changes will be made in the 1.x release series. Anyone using a semver-aware dependency manager should now pin to
zaptest, which is less likely to clash with other testing helpers.
zapcore.NewCore, which allows zap to work with concurrency-safe
fsyncstandard out on Linux systems.
CombineWriteSyncers, a convenience function to tee multiple
WriteSyncers and lock the result.
zaptest/observer. This makes it easier for particularly punctilious users to unit test their application's logging.
Thanks to @suyash, @htrendev, @flisky, @Ulexus, and @skipor for their contributions to this release.
This is the third release candidate for zap's stable release. There are no breaking changes.
zap.Anyare now correctly treated as binary blobs rather than
Thanks to @ansel1 and @suyash for their contributions to this release.
This is the second release candidate for zap's stable release. It includes two breaking changes.
#316: Zap's global loggers are now fully concurrency-safe (previously, users had to ensure that
ReplaceGlobals was called before the loggers were in use). However, they must now be accessed via the
S() functions. Users can update their projects with
gofmt -r "zap.L -> zap.L()" -w . gofmt -r "zap.S -> zap.S()" -w .
logoutput now correctly reports the logger's caller.
New(nil)continues to return a no-op logger,
NewNop()is now preferred. Users can update their projects with
gofmt -r 'zap.New(nil) -> zap.NewNop()' -w ..
github.com/uber-go/zapnow returns a more informative error.
Thanks to @skipor and @chapsuk for their contributions to this release.
This is the first release candidate for zap's stable release. There are multiple breaking changes and improvements from the pre-release version. Most notably:
zappackage. Code relevant largely to extension authors is now in the
zapcore.Coretype makes it easy for third-party packages to use zap's internals but provide a different user-facing API.
Loggeris now a concrete type instead of an interface.
This is a minor version, tagged to allow users to pin to the pre-1.0 APIs and upgrade at their leisure. Since this is the first tagged release, there are no backward compatibility concerns and all functionality is new.
Early zap adopters should pin to the 0.1.x minor version until they're ready to upgrade to the upcoming stable release.