All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning (despite its flaws).
spyf
to clojure.tools.logging.readable
.logger-factory
implementations were calling
library-specific static convenience methods for each call to get-logger
.
These methods have some baked-in setup overhead, which now only occurs during
instantiation of the associated logger-factory
.clojure.tools.logging.readable
."clojure.tools.logging.factory"
system property. For details, see the
README,
and the documentation for *logger-factory*.clojure.tools.logging.test
.Class/forName
when
determining whether logging implementation classes are available on the
classpath. This was done to allow testing of the various impl/*-factory
functions, and seems consistent with clojure internals.level
in logging adapters.Logger
and LoggerFactory
.spyf
, like spy
but takes a format string for the result.message
arg to logf
and logp
.clojure.tools.logging.impl
.clojure.tools.logging.impl
.spy
macro.log*
from logp
and logf
.Can you improve this documentation? These fine people already did:
Alexander Taggart & Alex MillerEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close