Closed TribuneX closed 1 year ago
Currently ktlint is called with log level debug which leads to a lot of log messages in case the hook is failing. It is sometimes hard to spot the actual rule violation. What about allowing to configure the log level to e.g. INFO?
ktlint
INFO
Thanks for the report. This seems something that would be addressed already in #163
Thx. This should address the large log output issue. Looking forward to this update.
Currently
ktlint
is called with log level debug which leads to a lot of log messages in case the hook is failing. It is sometimes hard to spot the actual rule violation. What about allowing to configure the log level to e.g.INFO
?