varnamelen icon indicating copy to clipboard operation
varnamelen copied to clipboard

Go analyzer checking that the length of a variable's name matches its usage scope

Results 5 varnamelen issues
Sort by recently updated
recently updated
newest added

Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.9.1 to 0.12.0. Release notes Sourced from golang.org/x/tools's releases. gopls/v0.12.0 This release contains a major rewrite of the way gopls computes and stores package information, with the...

dependencies

I would like to use this tool to ban short variable names completely, except the ones explicitly allowed in the configuration. However, when I set `max-distance: 0`, it does not...

enhancement

The current linter is not configurable in turns of analysis scope. It would be amazing to have the ability to switch of analysis for e.g. _test.go files or _generated.go files...

enhancement

Related to #1 I have a function with a series of lookups and casts as it traverses untyped JSON while reporting errors, i.e. ``` fooval, ok := root["foo"] if !ok...

I encountered an issue when using a generic type T in combination with the linter setting check-type-param: true. The following code results in a linting error: ``` func NewStorageValueUnexpectedError[T int...