Configurable logger

[vemv]

Linters' output can clog the REPL, particularly when working with 'legacy' projects.

Would be nice to have a configurable logger, which would follow a hierarchy as per usual (global -> per-member)

[thumbnail]

Recently i've played around with the idea of a configurable reporter for all linters/formatters to aid with #88 and #48. The reporter could be configured to output the warnings into a file, which one could continiously read using watch --color -n 1 cat ./<file>.

POC:

This would be an extra step though for the dev to remember. I wondered about reading a socket and printing unless the socket is mounted. ensuring that the linting is not lost.

[vemv]

Looking good!

In the end it'd be a configurable choice (stdout, file, ...) so feel free to proceed

[vemv]

which would follow a hierarchy as per usual (global -> per-member)

with this I had meant that similarly to strategies, there could be a default logger object passed to the stack, and each member (e.g. a specific linter) could replace it, or assoc things to it etc.

Our final design was different, guided for the need for unifying various loggers' output (for comprehensibility).

The tradeoff was perceived performance, as hinted in #116 (comment) ; but probably we'll be able to address it somehow.