Giulia Stocco

@sybaris Try removing this part `, e => e, verbsIndex:true`. 

Partially implemented in #114 for the expected num files tests. The remainder of the tests don't generally share exactly the same arguments so there is more limited room to use...

I did a quick test of this and System.Formats.Tar extracts in many cases fewer files than our existing implementation. Would require additional research to figure out which implementation is "correct"...

Next step could be to examine the test tar tar that has either 5 or 6 files depending on the api called to figure out which is correct.

@arunpradhan thanks for the feedback. There is currently no capability in the IDE extension to export a sarif/json of the results. If you want a standalone report you can use...

Changed the title of this issue to reflect a feature request for this. I'm not sure of the feasibility, as the IDE extensions operate on only open files, and do...

I'm not sure what property populates that field. It doesn't appear to be documented in the GitHub documentation for how the code scanning feature parses sarif: https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning. From this other...

I was able to confirm that this feature is currently only available for CodeQL Scanning.

@agr Sorry for the confusion. The correct way to provide the arguments on the command line is comma separated. This gets automatically split on commas by the `CommandLineParser` dependency, giving...

It looks like removing the extra newlines is a supported configuration change, but it requires a bit of refactoring as we currently use the default parser (https://github.com/commandlineparser/commandline/wiki/HelpText-Configuration). Its not clear...