You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pkg/golinters/nolintlint/internal/README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# nolintlint
2
2
3
3
nolintlint is a Go static analysis tool to find ill-formed or insufficiently explained `//nolint` directives for golangci-lint
4
-
(or any other linter, using this package)
4
+
(or any other linter, using this package)
5
5
6
6
## Purpose
7
7
@@ -15,7 +15,7 @@ func hash(data []byte) []byte {
15
15
}
16
16
```
17
17
18
-
In the above case, nolint directives are present but the user has no idea why this is being done or which linter
18
+
In the above case, nolint directives are present, but the user has no idea why this is being done or which linter
19
19
is being suppressed (in this case, gosec recommends against use of md5). `nolintlint` can require that the code provide an explanation, which might look as follows:
20
20
21
21
```Go
@@ -26,6 +26,6 @@ func hash(data []byte) []byte {
26
26
}
27
27
```
28
28
29
-
`nolintlint` can also identify cases where you may have written `// nolint`. Finally `nolintlint`, can also enforce that you
29
+
`nolintlint` can also identify cases where you may have written `// nolint`. Finally,`nolintlint`, can also enforce that you
30
30
use the machine-readable nolint directive format `//nolint:all` and that you mention what linter is being suppressed, as shown above when we write `//nolint:gosec`.
0 commit comments