-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server: address golangci var-naming issues #17624
server: address golangci var-naming issues #17624
Conversation
Signed-off-by: Ivan Valdes <[email protected]>
//revive:disable:var-naming | ||
func (s *storeRecorder) JsonStats() []byte { return nil } | ||
|
||
//revive:enable:var-naming |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added this ignores, as it comes from v2's (*recorder) JsonStats().
@@ -26,7 +26,7 @@ import ( | |||
) | |||
|
|||
const ( | |||
ENV_VERIFY_VALUE_LOCK verify.VerificationType = "lock" | |||
EnvVerifyValueLock verify.VerificationType = "lock" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though this is exported, I just renamed it as it is used only by the backend_tests
package, which is in the same directory but in a different package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @ivanvc, another one tidied up!
This PR addresses minor var-naming violations from the server directory.
Part of #17578
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.