-
Notifications
You must be signed in to change notification settings - Fork 646
When build fails with errors that do not match known problem matchers, print it to output channel #732
Comments
I am able to see the errors. See below where I have a struct "ABC" and I have wrongly spelt "Hello" as "hello" However, I only see the error, when I make a change in the file and save which triggers the build. Can you confirm that you see the same as well? If yes, then the way to fix this would to be to trigger save on when the active editor changes. |
@ramya-rao-a no, the problem here is different from yours. even i change a file and then save it, vscode-go doesn't notify me the error |
Do you see any errors when you run |
hi @ramya-rao-a , i just created a brand new project and i can see the same with you.
but with my k8s project, it didn't notice me that error
and i tried to go build that package but got error:
it looks like a golang error, but all my tests run on the same machine. |
The Go extension depends on the output of Without fixing the golang errors that you are seeing, I don't think there is anything the the Go extension can do, am sorry :( One thing that can be done, is that we can show a message saying |
The PR #735 will help with this |
With the latest update (0.6.53), build errors such as the above will be displayed in the output window and will be mapped to the first line of the file i.e the first line of the file will get a red squiggly pointing to the error. |
for example, i have a struct
but i try to construct an instance like this:
checkIfActive is incorrect , it should be
CheckIfActive
, but vscode-go doesn't detect this.vscode-go version:0.6.52
vscode version:1.8.1
os: Ubuntu 16.04.1 LTS KDE 64bit
i have update all dependencies of vscode-go by running:
my user settings.json:
The text was updated successfully, but these errors were encountered: