add option around for //nolint directive

[kcmvp]

Your feature request related to a problem? Please describe.

it's not related to a problem

Describe the solution you'd like.

As far as we know we can use //nolint directive to bypass linter check.
but I found this directive is abused in our team.

in follow two cases
1: on file level

//nolint:unparam
package pkg

2: on block level

//nolint:all
func allIssuesInThisFunctionAreExcluded() *string {
  // ...
}

my questions are(feature request) are:

1. Is there anyway to disable these two usage? (or supply an option to disable it
2. in the final report can we add a statistics report about usage of //nolint?

with these two features we can monitor (control the abuse) //nolint and know well about code base quality.

Describe alternatives you've considered.

it's best implemented as part of the golangci-linter for nolint directive process for performance consideration.

thank you all very much to supply such useful too!

Additional context.

No response

[boring-cyborg]

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

[ldez]

related to #3015

[kcmvp]

@ldez disable is not I want. can we add statistics data in the final report? (numbeer of //nolint)

[kcmvp]

so in this way we can monitor the total number of ignores by categroy: package, block, line

[ldez]

You can use something like that: grep -rE '// ?nolint' | wc -l

[kcmvp]

as I want to use those data in my CI process, so it's better to implement in the library.

[ldez]

You can use bash in your CI.

[ldez]

I haven't closed the issue, we will see if there is some traction on it.

For now, using bash is the best solution for you.

[kcmvp]

Thank you very much!
this tools aims to improve source code quality, I simply think those data is one of the indexes.