-
Notifications
You must be signed in to change notification settings - Fork 645
gotype-live is reporting errors based off out-of-date file content #943
Comments
That's weird. Live errors should really act on the live file :) One thing to note is that live error reporting kicks in when you start making changes to the file. cc @tylerb |
I agree :) Closing and opening the file does not display the errors right away, until I start typing. I opened the file and created a new line (L280), and the error started showing up. |
This is most likely related to the PR that was recently merged. This issue should go away once the next release of vscode-go comes out.
…On Apr 25, 2017, 7:41 PM -0600, Thinh Nguyen ***@***.***>, wrote:
I agree :)
Closing and opening the file does not display the errors right away, until I start typing.
The errors are not really related to the line at all, and for the most part points to another part of the code completely (another file). Here's an example:
I opened the file and created a new line (L280), and the error started showing up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#943 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAEUlLVbVp7GrAly7JZOeqgtlTeUFgUWks5rzqCtgaJpZM4NHfxM).
|
The next release would be early next week which will have the fix for the issue of errors from other files showing up in the current file. @Taik if you don't mind can you side load the Go extension from master (See https://github.com/Microsoft/vscode-go/wiki/Building,-Debugging-and-Sideloading-the-extension-in-Visual-Studio-Code#sideloading-the-extension) to confirm that the fix in master fixes your issue? |
I just gave it a try, and it seems like it fixed it. Thanks for the awesome plugin! |
Fix is out in the latest update (0.6.60) |
Thanks much, @ramya-rao-a!! |
I also have the problem in 0.6.62. |
@wangxufire Please share a video/gif of the problem you are seeing. Preferably using a small simple code |
When using live error reporting, gotype-live sometimes returns errors based off out-of-date file content. It's very noticeable when switching between branches where an extra parameter was added to function/method signatures (in my case, I'm extending functions to take in
context.Context
).My current setup:
Live error config:
The text was updated successfully, but these errors were encountered: