Getting native linter output

[pascalberger]

Hi,
I'm the author of a bunch of addins for the Cake Build automation system to parse linting output, report them to pull requests and build servers and create reports (https://cakeissues.net/). The addins won't take care of calling linters, but focus on processing the output generated by linters.

I had the idea that it could be nice to combine it together with linters in an all-in-one docker image. Megalinter could serve as the base image in this case, taking care of determine what linter should be called, calling them and then provide log files as output which could be processed further by the Cake addins.

I'm aware that this is not the original use-case for megalinter and searched through docs, but could not find if it is possible to have megalinter just call the linters and provide the linter output (not reports created by megalinter)?

[echoix]

The different kinds of outputs are created by "reporters", différent Python classes, that can be enabled and disabled. As such, would disabling all of them do what you want? Or would you be writing a new reporter and access the info you'd need to do your processing?

[pascalberger]

The addins already contain parsers for different linters, being it tool specific formats, like an EsLint json output, or standardized formats like a SARIF file.

What I'm looking for is a way to define the output format of the linters (e.g. for tflint I would require a SARIF file), and then have megalinter just call the linter with the correct arguments to get the desired output file written somewhere.

Does this make sense?