-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Enable lint on go1.7 #135
Enable lint on go1.7 #135
Conversation
@@ -33,6 +33,8 @@ else | |||
@echo "Not installing golint, since we don't expect to lint on" $(GO_VERSION) | |||
endif | |||
|
|||
VET_SKIP_ERRORF=grep -v -e "possible formatting directive in Error call" |
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.
Is this a pervasive issue in zap, or is there one particular place where vet complains?
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.
calls to testify's assert.Error
, which i guess i can just rewrite.
We should keep the checks as It seems to only happen if the vendor directory is available: $ go tool vet flag_test.go
flag_test.go:61: possible formatting directive in Error call
$ mv vendor vendor_
$ go tool vet flag_test.go
$ mv vendor_ vendor
$ go tool vet flag_test.go
flag_test.go:61: possible formatting directive in Error call It looks like if the type is available, |
Should we disable the printf checks when running vet for now? |
lgtm, can you add a comment to why we disabled printf checks. |
No description provided.