Add gostyle-action #68
k1LoWAnnotations
7 errors
|
Test:
rl.go#L39
[gostyle.getters] Function and method names should not use a Get or get prefix, unless the underlying concept uses the word “get” (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use Counts over GetCounts. (ref: https://google.github.io/styleguide/go/decisions#getters): Get
|
|
Test:
rl.go#L81
[gostyle.recvnames] Receiver variable names must be abbreviations for the type itself: rl
|
|
Test:
testutil/limiter.go#L82
[gostyle.getters] Function and method names should not use a Get or get prefix, unless the underlying concept uses the word “get” (e.g. an HTTP GET). Prefer starting the name with the noun directly, for example use Counts over GetCounts. (ref: https://google.github.io/styleguide/go/decisions#getters): Get
|
|
Test:
rl_test.go#L17
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name): rl_test<-[Test]->TestRL
|
|
Test:
rl_test.go#L17
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name): rl_test<-[RL]->TestRL
|
|
Test:
rl_test.go#L87
[gostyle.repetition] When naming exported symbols, the name of the package is always visible outside your package, so redundant information between the two should be reduced or eliminated. (ref: https://google.github.io/styleguide/go/decisions#package-vs-exported-symbol-name): rl_test<-[RL]->BenchmarkRL
|
|
Test
Process completed with exit code 1.
|