You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installed latest gopls. Set it up with vim-ale. Works great!
Opened a (test) file that has the following build tag at the top:
// build +integration
What did you expect to see?
Completions and diagnostics in that file.
What did you see instead?
No completions or diagnostics in that file. If I remove the build tag, I start getting diagnostics. Oddly enough, if I add the tag back, I still get diagnostics. Perhaps there's some caching happening then?
It would be great to have completion and diagnostics for every file I'm editing. I imagine this might be difficult for arch tags and such, but it would be good to customize this. For example, golangci-lint lets you set build tags to pass when running it.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Installed latest gopls. Set it up with vim-ale. Works great!
Opened a (test) file that has the following build tag at the top:
What did you expect to see?
Completions and diagnostics in that file.
What did you see instead?
No completions or diagnostics in that file. If I remove the build tag, I start getting diagnostics. Oddly enough, if I add the tag back, I still get diagnostics. Perhaps there's some caching happening then?
It would be great to have completion and diagnostics for every file I'm editing. I imagine this might be difficult for arch tags and such, but it would be good to customize this. For example, golangci-lint lets you set build tags to pass when running it.
The text was updated successfully, but these errors were encountered: