Changelog for logging-effect-1.1.2
1.1.2
Other changes
- Increased upper bound of
time
1.1.1
withBatchedHandler
no longer prints empty log messages. Previously, if you ran a program that didn't log but usedwithBatchedHandler
(or anything that used that), an empty log message would be output. Thanks to @codedmart for fixing this.
1.1.0
Breaking changes:
-
MonadLog
no longer haslogMessage
as a function. It now haslogMessageFree
which takes a free monoid of log messages. If you were just usinglogging-effect
then this won't affect you, aslogMessage
still exists with the same signature outside the type class. -
MonadLog
now comes with a law that states that logging is a monoid homomorphism. This essentially means that you have to treat all log messages uniformly. -
Pass-through instances for all "stock" monad transformers have been added (all of
transformers
,CatchT
from exceptions andFreeT
/FT
fromfree
). -
WithSeverity
now has instances ofTraversable
andFoldable
-
WithTimestamp
now has instances ofEq
,Ord
,Read
andShow
.
Additions:
-
A set of convenience functions have been added for quickly logging with severity. The combinators are:
logDebug
,logInfo
,logNotice
,logWarning
,logError
,logCritical
,logAlert
andlogEmergency
. -
mapLogMessage
got a companion functionmapLogMessageM
that works with monadic tranformations.
Other
-
Many documentation bug fixes.
-
INLINEABLE pragmas added.
1.0.0
- Initial release