What version of Go are you using (go version)?

$ go version
go version go1.11.5 darwin/amd64

Using revision 8aaa148 of tools.

Does this issue reproduce with the latest release?

N/A

What operating system and processor architecture are you using (go env)?

$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/alex/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/alex/.go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/opt/go/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/alex/Projects/Transparensee/enclosure-core/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qs/wpmg19r12_9_nz7pvvs2_82r0000gn/T/go-build840369688=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

1. I ran a go generate command, which generates Go files. In this case, the generated code previously defined a struct with a field NeighborhoodUIDs; the generate run renamed this to NeighborhoodUids.
2. In VSCode, I now wanted to edit other files referencing this struct in order to update all the calling code that uses this field.
3. Gopls insists that NeighborhoodUids is incorrect and that the old name is correct.

This implies that Gopls is not correctly monitoring the files on disk. It's only taking into account the changes I make through the editor.

What did you expect to see?

Gopls should always reflect the current state of files on disk, not just edits made in the editor that uses Gopls.

What did you see instead?

See above.

gopls.log.zip