-
Notifications
You must be signed in to change notification settings - Fork 660
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
- Loading branch information
Showing
13 changed files
with
78 additions
and
54 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
issues: | ||
max-same-issues: 0 | ||
linters: | ||
enable: # please keep this alphabetized | ||
- gofmt | ||
- goimports | ||
- testifylint | ||
linters-settings: # please keep this alphabetized | ||
goimports: | ||
local-prefixes: go.etcd.io # Put imports beginning with prefix after 3rd-party packages. | ||
testifylint: | ||
enable-all: true | ||
formatter: | ||
# Require f-assertions (e.g. assert.Equalf) if a message is passed to the assertion, even if | ||
# there is no variable-length variables, i.e. require require.NoErrorf for both cases below: | ||
# require.NoErrorf(t, err, "whatever message") | ||
# require.NoErrorf(t, err, "whatever message: %v", v) | ||
# | ||
# Note from golang programming perspective, we still prefer non-f-functions (i.e. fmt.Print) | ||
# to f-functions (i.e. fmt.Printf) when there is no variable-length parameters. It's accepted | ||
# to always require f-functions for stretchr/testify, but not for golang standard lib. | ||
# Also refer to https://github.com/etcd-io/etcd/pull/18741#issuecomment-2422395914 | ||
require-f-funcs: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.