ssgreg / nlreturn
Checks for a new line before return and branch statements.
☆28Updated last year
Alternatives and similar repositories for nlreturn
Users that are interested in nlreturn are comparing it to the libraries listed below
Sorting:
- Golang linter that encourages you to use a separate _test package☆50Updated 3 weeks ago
- Go linter to detect erroneous multiplication of duration values☆47Updated last year
- Golang linter to check the errors handling expressions☆52Updated 4 years ago
- Simple linter to check that your code does not contain non-ASCII identifiers☆27Updated 3 weeks 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 3 weeks ago
- ☆42Updated 5 months ago
- Linter that checks that comments end in a period☆46Updated last month
- Check that no init functions are present in Go code.☆41Updated 4 years ago
- golang linter to detect named returns☆28Updated 2 weeks ago
- Go linter that checks if package imports are in a list of acceptable packages.☆164Updated 2 months ago
- A linter to ensure that slices are not initialized with non-zero length☆75Updated 4 months ago
- Golang linter to use strconv☆40Updated 2 months ago
- Go linter for forbidding identifiers☆140Updated 4 months ago
- Check that no globals are present in Go code.☆113Updated this week
- GoDoX extract speficic comments from Go code based on keywords☆17Updated 4 months ago
- A linter that handles struct tags.☆54Updated last month
- 🚔 Enforce field tags in (un)marshaled structs☆38Updated 2 weeks ago
- Analyzer: fourcetypeassert finds type assertions which did forcely☆39Updated 3 months ago
- ☆53Updated 7 months ago
- A curated list of Go code formatters (like gofmt)☆39Updated 4 years ago
- tparallel finds inappropriate usage of `t.Parallel()` method in your Go test codes☆26Updated 11 months ago
- intrange is a program for checking for loops that could use the Go 1.22 integer range feature.☆29Updated last week
- Go linter for checking that your code uses short syntax for if-statements whenever possible.☆18Updated 2 years ago
- clear go error wrapping with caller☆51Updated last year
- Detect deeply nested if statements in Go source code☆43Updated 3 years ago
- Go linter that checks types that are json encoded - reports unsupported types and unnecessary error checks☆41Updated 2 weeks ago
- The Golang linter that checks that there is no simultaneous return of `nil` error and an invalid value.☆66Updated 3 weeks ago
- ☆21Updated 5 months ago
- Accept Interfaces, Return Concrete Types☆69Updated 3 weeks ago
- ☆26Updated 3 years ago