File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -71,9 +71,9 @@ That is all the configuration that is required to run a custom linter in your pr
71
71
72
72
Custom linters are enabled by default, but abide by the same rules as other linters.
73
73
74
- If the disable all option is specified either on command line or in ` .golang .yml` files `linters.disable-all: true `, custom linters will be disabled;
74
+ If the disable all option is specified either on command line or in ` .golangci .yml` files `linters.default: none `, custom linters will be disabled;
75
75
they can be re-enabled by adding them to the `linters.enable` list,
76
76
or providing the enabled option on the command line, `golangci-lint run -Eexample`.
77
77
78
- The configuration inside the `settings` field of linter have some limitations (there are NOT related to the plugin system itself) :
78
+ The configuration inside the `linters. settings` field of linter have some limitations (there are NOT related to the plugin system itself) :
79
79
we use Viper to handle the configuration but Viper put all the keys in lowercase, and `.` cannot be used inside a key.
You can’t perform that action at this time.
0 commit comments