chore(deps): bump the dependencies group across 1 directory with 3 updates #30
Annotations
9 errors and 1 warning
|
Test:
testdata/example/main.go#L9
[gostyle] reported by reviewdog 🐶
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Getter
Raw Output:
./main.go:9:13: [gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Getter
|
|
Test:
testdata/example/main.go#L5
[gostyle] reported by reviewdog 🐶
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Query
Raw Output:
./main.go:5:12: [gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Query
|
|
Test:
testdata/example/main.go#L10
[gostyle] reported by reviewdog 🐶
[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 ): GetSomething
Raw Output:
./main.go:10:2: [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 ): GetSomething
|
|
Test
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Getter
|
|
Test
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Query
|
|
Test
[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 ): GetSomething
|
|
Test
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Getter
|
|
Test
[gostyle.ifacenames] By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun. (ref: https://go.dev/doc/effective_go#interface-names ): Query
|
|
Test
[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 ): GetSomething
|
|
Test
Restore cache failed: Dependencies file is not found in /home/runner/work/gostyle-action/gostyle-action. Supported file pattern: go.sum
|