Fork me on GitHub

> Would strongly recommend against using > Timbre through tools.logging unless you absolutely must I just noticed Until today, I thought that abstracting logging implementations via was a good practice, especially for libraries, otherwise everything that consumes it downstream is forced to have timbre -or whatever implementation the library uses- as a dependency as well. This can also be an issue if for instance you want to set up a custom appender (e.g. JSON) and you're using a different logger implementation in your artifact, in which case you have to configure the appender at least twice. So I guess my question is what are some practical reasons not to use with timbre?


Grep for ; No support within that file


I see, should have seen that the first time 😞 Thanks, could be a potential problem because we need some of that information but I'll see what I can do.