Changelog for logging-effect-1.2.2
1.2.2
Other Changes
- Increased upper bound of
freeandtime.
1.2.1
Other Changes
- Increased upper bound of
baseto allow < 4.11.
1.2.0
Major Changes
-
withFDHandlernow explicitly flushes the file handle whenever log entries are rendered out. Thanks to @filterfish for identifying this omission that could lead to log messages being dropped.Upgrade steps: no changes other than updating
logging-effect.
1.1.3
Other Changes
- Increased upper bound of
timeto allow < 1.9.
1.1.2
Other changes
- Increased upper bound of
time
1.1.1
withBatchedHandlerno 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:
-
MonadLogno longer haslogMessageas a function. It now haslogMessageFreewhich takes a free monoid of log messages. If you were just usinglogging-effectthen this won't affect you, aslogMessagestill exists with the same signature outside the type class. -
MonadLognow 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,CatchTfrom exceptions andFreeT/FTfromfree). -
WithSeveritynow has instances ofTraversableandFoldable -
WithTimestampnow has instances ofEq,Ord,ReadandShow.
Additions:
-
A set of convenience functions have been added for quickly logging with severity. The combinators are:
logDebug,logInfo,logNotice,logWarning,logError,logCritical,logAlertandlogEmergency. -
mapLogMessagegot a companion functionmapLogMessageMthat works with monadic tranformations.
Other
-
Many documentation bug fixes.
-
INLINEABLE pragmas added.
1.0.0
- Initial release