nakabonne / nestifLinks
Detect deeply nested if statements in Go source code
☆43Updated 3 years ago
Alternatives and similar repositories for nestif
Users that are interested in nestif are comparing it to the libraries listed below
Sorting:
- dogsled is a Go static analysis tool to find assignments/declarations with too many blank identifiers.☆73Updated last year
- Golang linter to check the errors handling expressions☆52Updated 4 years ago
- A Go library for encoding structs into Header fields.☆46Updated last year
- Go linter to detect erroneous multiplication of duration values☆47Updated last year
- An analyzer that checks for pointers to enclosing loop variables.☆38Updated last year
- ☆53Updated 7 months ago
- Fixes simple parse errors automatically. Works great in combination with goimports.☆86Updated 5 years ago
- ☆97Updated 5 months ago
- Go linter that checks types that are json encoded - reports unsupported types and unnecessary error checks☆41Updated 2 weeks ago
- Linter that checks that comments end in a period☆46Updated last month
- A linter to ensure that slices are not initialized with non-zero length☆75Updated 4 months ago
- ☆21Updated 5 months ago
- nargs is a Go static analysis tool to find unused arguments in function declarations.☆86Updated 2 weeks ago
- Linter for errors.Is and errors.As☆46Updated 5 years ago
- ☆41Updated 5 years ago
- Check that no init functions are present in Go code.☆42Updated 4 years ago
- Go Embed experiments☆30Updated 3 years ago
- A simple terminal UI for Go linters☆81Updated 4 years ago
- A linter that handles struct tags.☆54Updated last month
- golang linter to detect named returns☆28Updated 3 weeks ago
- ☆121Updated 11 months ago
- Linter checks that printf-like functions are named with `f` at the end.☆26Updated 2 months ago
- ☆26Updated 3 years ago
- unindent stuff☆35Updated 4 years ago
- nakedret is a Go static analysis tool to find naked returns in functions greater than a specified function length.☆130Updated this week
- Analyzer: helps uncover bugs by reporting a diagnostic for mistakes of *sql.Rows usage.☆91Updated last year
- tparallel finds inappropriate usage of `t.Parallel()` method in your Go test codes☆26Updated 11 months ago
- Checks for a new line before return and branch statements.☆28Updated last year
- Format Go's benchmarking output☆88Updated 3 years ago
- The Golang linter that checks that sentinel errors are prefixed with the `Err` and error types are suffixed with the `Error` or `Errors`.☆25Updated this week