Print errors, tracing and debugging information to stderr instead of stdout #1308
Conversation
…stdout Ideally only the output of rule violations is printed to stdout so that it can be redirected to the reporters. Normal log lines most likely break the format of the reporter and therefore should be printed to stderr. Closes pinterest#1137
|
I believe @Tapchicoma had a slightly different idea - to use some proper logging solution for that -> #589 (here comes the joke about log4j indeed) |
In the end that will be a better solution. Meanwhile, this PR still adds value as it once more has been checked that no output is written to stdout that interferes with the reporters. |
@romtsn See #1327 for implementation of logging framework. This PR can be closed once that PR has been approved and merged. |
|
yeah let's try to push #1327 through, closing this |
Description
Ideally only the output of rule violations is printed to stdout so that it can be redirected
to the reporters. Normal log lines most likely break the format of the reporter and therefore
should be printed to stderr.
Closes #1137
Checklist
CHANGELOG.mdis updated