-
-
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
Broken code is not reported as broken by the linter #2533
Comments
I tracked down this issue to golangci/golangci-lint#276 |
You can workaround this by including |
is it documented somewhere? It was really frustrating |
I just tried it, enabling |
we discovered that while looking into a similar issue: #2475 (comment) |
looks like that workaround is no longer working @bhcleek in the terminal it's still 0 exit code (successful) |
the commit from golangci-lint that breaks the workaround is 95ec0cf21ea4720ec9555c43176ab8b1d1b035f2 I just bisected it |
Thanks for the heads up. There's not much that vim-go can do about this; ultimately, it's a bug in golangci-lint. |
add this to your .vimrc:
When you want to save and check errors, hit F6. It will have the behavior you expect. |
What did you do? (required: The issue will be closed when not provided)
What did you expect to happen?
Get the possible lines where the code is broken, it used to be like that with gometalinter
What happened instead?
No errors were reported
Configuration (MUST fill this out):
vim-go version:
master
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):vimrc
Vim version (first three lines from
:version
):8.1
Go version (
go version
):1.13
Go environment
go env
Output:The text was updated successfully, but these errors were encountered: