Enabling SARIF_REPORTER overrides TEXT_REPORTER features

[bdovaz]

If I activate SARIF_REPORTER and TEXT_REPORTER at the same time, the following happens:

1. A folder "linters_logs" is created with all linters logs in *.log format (CORRECT).
2. A folder "sarif" is created with all the linters logs in *.sarif format (CORRECT).
3. A file "megalinter-report.sarif" is created in the root replacing the file "megalinter-report.log" (WRONG).

Why do I lose the complete log in text format which is equivalent to what is shown by console? It is very useful to inspect it later.

[nvuillam]

When we use SARIF reporter, we call the linters with arguments telling them to output the result in SARIF and not in "human readable" text

Calling twice the linters with text mode then SARIF mode would double the performances and that would be not acceptable, but I recently found a library that seems to be able to convert SARIF to human text, i've not tested it yet but that could be an interesting evolution to implement someday on MegaLinter :)

[bdovaz]

Well, in the same way that you documented several topics about the TAP reporter, it should be documented that there are reporters that can "coexist" at the same time but others, as in this case TEXT vs SARIF, cannot. That is, if SARIF is activated, the text reporter stops working.

[Kurt-von-Laven]

Happy to accept a pull request to clarify this in the documentation. On a related note, I see that docs/reporters.md is currently missing SARIF, so that is another place to update in addition to docs/reporters/SarifReporter.md.

[nvuillam]

Well, in the same way that you documented several topics about the TAP reporter, it should be documented that there are reporters that can "coexist" at the same time but others, as in this case TEXT vs SARIF, cannot. That is, if SARIF is activated, the text reporter stops working.

Text reporter just store the console output of linters, so technically it still works even if the content is sarif :D
But I get your point, I hope that someday i'll find the time to implement the sarif-to-human for such case ^^