lumberjack 1.0.0.0 → 1.0.0.1

raw patch · 3 files changed

+17/−8 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• CHANGELOG.md +6/−0
• example/ExampleLog.hs +2/−2
• lumberjack.cabal +9/−6

@@ -1,5 +1,11 @@ # Revision history for lumberjack +## 1.0.0.1 -- 2021-06-27++  * Fix issue #2: use eta expansion example to avoid loss of deep+    skolemisation support under the simplified subsumption rules in+    GHC 9 [thanks to Felix Yan for the report].+ ## 1.0.0.0 -- 2020-12-20    * No longer Beta, so major version is now 1.0, although functionality

@@ -66,7 +66,7 @@   getLogAction = ask  instance LoggingMonad T.Text MyMonad where-  adjustLogAction = local+  adjustLogAction a = local a  exampleStringLoggingInMyMonad :: MyMonad () exampleStringLoggingInMyMonad = do@@ -92,7 +92,7 @@   getLogAction = ask  instance LoggingMonad LogMessage MyMonad2 where-  adjustLogAction = local+  adjustLogAction a = local a  -- The above is sufficient to log LogMessage objects, but for -- convenience, Text can be logged directly as well, using the

@@ -1,6 +1,6 @@ cabal-version:       >=1.10 name:                lumberjack-version:             1.0.0.0+version:             1.0.0.1 synopsis:            Trek through your code forest and make logs description:         This is a logging facility.  Yes, there are many, and this is the one                      with a beard, wearing flannel and boots, that gets the job done.  It's@@ -8,7 +8,7 @@                      logger is designed to be straightforward to use, provide a good set of                      standard features, and be useable across a broad set of code.                      .-                     * Logging is a monadic activity.  This activity is most often+                     * Logging itself is a monadic activity.  This activity is most often                        performed in a monad stack with a MonadIO context to allow                        writing to files.                      . @@ -18,11 +18,14 @@                        be specified at startup time without requiring changes in the                        code from which log messages are being generated.                      .-                     * The logging implementation code can use cofunctors to adjust-                       existing logging.+                     * The logging implementation code can use contravariant functors to+                       adjust existing logging.                      .-                     * Main code will typically retrieve the logging actions from a-                       Reader context in your monad stack.+                     * Main code will typically retrieve the logging actions from a Reader+                       context in your monad stack.  That said, Log actions are not tied+                       to an enclosing Monad.  There are helpers to support a Monad which+                       can store Log actions, but Log actions can also be explicitly+                       passed and used.                      .                      * The prettyprinter package is used for formatting.