Support closure based configuration so that the logging operations aren't stuck with singleton configuration about timbre HOT 4 CLOSED

I handle the simultaneous use of simple singleton atom based configuration and closure based configuration here: https://github.com/bitemyapp/bulwark/ if you wanted an example.

The test cases use the closure version IIRC.

from timbre.

I'd also like this. There are multiple uses for a logging library which cannot be achieved by simply implementing additional appenders.

from timbre.

Hi Chris,

Sure, I'm open to this idea. Shouldn't be too difficult to do - would just need to move the atom-watch logic into a [memoized] fn of a config map. Then we can introduce a variation of the standard logging macro that takes an explicit config map and passes it through this fn on each call.

I'm going to be tied up with some high-priority work for at least a couple more weeks though, so PR's welcome!

Just for interest - could you describe your use case? Note that there's already a with-log-level for the common case of just wanting to adjust the logging level temporarily.

Cheers :-)

from timbre.

Done on dev branch; will be pushing an alpha release later today.

from timbre.