Skip to content

Commit

Permalink
Update RULES_DESCRIPTIONS.md (#1134)
Browse files Browse the repository at this point in the history
Describe var-naming's limitation on evaluating test file functions.
  • Loading branch information
ivanvc authored Nov 18, 2024
1 parent 0afba4f commit 655e606
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion RULES_DESCRIPTIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -997,7 +997,7 @@ _Configuration_: N/A
## var-naming
_Description_: This rule warns when [initialism](https://go.dev/wiki/CodeReviewComments#initialisms), [variable](https://go.dev/wiki/CodeReviewComments#variable-names) or [package](https://go.dev/wiki/CodeReviewComments#package-names) naming conventions are not followed.
_Description_: This rule warns when [initialism](https://go.dev/wiki/CodeReviewComments#initialisms), [variable](https://go.dev/wiki/CodeReviewComments#variable-names) or [package](https://go.dev/wiki/CodeReviewComments#package-names) naming conventions are not followed. It ignores functions starting with `Example`, `Test`, `Benchmark`, and `Fuzz` in test files, preserving `golint` original behavior.
_Configuration_: This rule accepts two slices of strings and one optional slice with single map with named parameters.
(it's due to TOML hasn't "slice of any" and we keep backward compatibility with previous config version)
Expand Down

0 comments on commit 655e606

Please sign in to comment.