Treat "Found unknown linters" warning as an error

[jmdacruz]

Is your feature request related to a problem? Please describe.
Currently, if I use a nolint directive with an unknown linter (regardless on whether the line has any linter errors or not), the result is a warning that looks like this:

WARN [runner/nolint] Found unknown linters in //nolint directives: foobar

The problem is that if such a directive is added by mistake (e.g., a typo on the linter name), this will masquerade the actual linter error (since the exit status of golangci-lint is 0 with this warning). I couldn't find an obvious configuration parameter to handle these scenarios properly.

Describe the solution you'd like
I would expect the output of golangci-lint to be non-zero for these scenarios, or somehow configure warnings to be treated as errors. Another alternative would be for the nolintlint linter to catch these (I tried playing with allow-unused, but did not get what I expected)

Describe alternatives you've considered
N/A

Additional context
N/A

[boring-cyborg]

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

[iwankgb]

The problem seems to be a bit more nuanced: Nolint.shouldPassIssue() applies ignored ranges to all the linters instead of Nolitn only.

[iwankgb]

I have a fix for your problem but I'm struggling with testing it.