Any way to suppress error code from Roslynator when it detects issues in code but runs successfully?

[davewichers]

I simply want to generate the Roslynator reports on a bunch of different folders, even if there are findings found in them. The code I'm using bails out if Roslynator detects an error and then won't run on the next folder.

Is there any way to configure Roslynator to NOT return an error code when it successfully runs, even if it finds issues in the code its analyzing?

This is related to issue: #759, which added this feature. While I can understand adding this as a feature when issues are detected, I can see situations where someone could want to have detected issues NOT considered an error when running Roslynator.

Could a command line option be added, or a configuration setting, or something, so that a successful run does NOT return an error code even when issues are found in the code?

[josefpihrt]

The code I'm using bails out if Roslynator detects an error and then won't run on the next folder

It's possible to add such option but can I ask you why can't you just ignore app exit code?

[davewichers]

I could, but I think it would be a reasonable, and relatively easy feature to add, so people don't have to code around this behavior. They could simply choose to configure Roslynator to only generate an error code when the scan fails, rather than when it finds an issue.