-
Notifications
You must be signed in to change notification settings - Fork 646
Types are not being automatically updated/checked #2848
Comments
UPDATE I disabled every plugin I have, other than the Go plugin, and the issue persists. |
I've been able to replicate the issue in such a way I can share the steps (code is shared first and steps at the bottom of this comment). Project structure:
And the actual files themselves: // main.go
package main
import "play/config"
func main() {
config.Hello("Bob")
} // go.mod
module play
go 1.12
// config/config.go
package config
import "log"
func Hello(u string) {
log.Println("Hello", u)
} Steps to reproduce:
Is this the expected behaviour? Is there a way to tell VSCode to update? In this small project, just opening the |
Apologies for not getting to this sooner @OmisNomis @stamblerre The language server is powering the auto completion & diagnostics, modules are in use. Can you please take a look here? |
We have not yet finished implementing support for watching files changed outside of the editor in |
@ramya-rao-a: golang/go#31553 is now closed and will be part of |
Thanks @stamblerre For folks who want to try the fix before the next version is out, please try out
|
Describe the bug
If I'm working on a Go project and I change a type the IntelliSense type checking isn't updated.
This seems to only happen in large projects, so it's hard to provide reproducible steps, but if a type is changed somewhere else in the project that should cause an error, it doesn't.
Equally, if there is a type error and I fix it, the error persists because it doesn't acknowledge it has been updated.
Eventually, I have to close VSCode down completely and re-open it to get it to recognise the difference - which is annoying.
VSCode settings
Preferences: Open Settings (JSON)
To Reproduce
Expected behavior
I expect the new type to be registered, so the error goes away or is shown.
Screenshots
If applicable, add screenshots to help explain your problem.
System information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: