Releases: go-playground/log
Release 6.2.2
What was fixed?
Added resetting of the email template when changing email information, otherwise new values were not reflected. see #23 for details thanks @Chiiruno for the PR
Release 6.2.1
What was fixed?
Allowing setting of the email config values individually was racey, updated to use a single method and synchronized with a RWMutex.
Release 6.2.0
What's new?
Added ability to change email handler information after initialization, but synchronization of the change is still the user's responsibility. see #19 for details, thanks @Chiiruno for the PR!
also fixing the versioning, I accidentally cut the last release as 6.0.1 instead of 6.1.1.
Release 6.0.1
What was fixed?
Fixed error prefixes being extracted from error.Cause and properly appended to the error when using WithError thanks @andreiko for reporting
Release 6.1.0
What's changed?
updated for new errors package changes.
Release 6.0.0
What's new?
This is a major version bump to v6.0.0, for most there will be no changes at all, but was a possibility for those using pkg/errors so just being cautious.
- Exposed
HandleEntryto allow for centralized logging. - Add ability to customize
WithErrorfunctionality- uses go-playground/errors by default as the default
WithErrorfunction - custom pkg/errors
WithErrorfunction exists undererrors/pkg - custom segmentio/errors-go
WithErrorfunction exists undererrors/segmentio
- uses go-playground/errors by default as the default
Release 5.0.2
What was fixed?
Corrected setting the Timestamp at time of logging.
Release 5.0.1
What was fixed?
Added missing MarshalJSON and UnmarshalJSON to Level
Release 5.0.0
v5.0.0 Released! what's changed/improved?
- Removing pooling entries
- Allowing default/global fields you want on all entries
- Allowing sharing of fields between entries
- Allowing tracing using
WithTraceto be used with any log level - Adding convenient methods to store and retrieve the log Entry from a context.Context for request scoped entries.
- Simplified log Handlers
- Added
WithErrormethod. WithError()has support for errors package, wrapper error info will be used.WithError()if it is not a wrapped error will fetch the program line and file info automatically.
Why do we not use a map like other loggers for WithFields?
- maps have overhead that is not used or helpful.
- using a map for fields entries does not guarantee the order of the entries.
Release 4.3.0
What's new?
- Added SetExitFunc() for overriding of the exist function called by
Fatal()andFatalf()calls Thanks @sb10 - Added
strconv.AppendFloat(...) - Renamed
examplesto_examplesto avoid pulling in dependencies, if any, in the examples.