-
-
Notifications
You must be signed in to change notification settings - Fork 970
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jump to declaration not working in Go modules #977
Comments
please download liteide x34.2 and check |
Unfortunately, this one still not working Example project: /home/myuser/projects/modtest/cli/servio ==> main.go, reference-import "modtest/servio". /home/myuser/projects/modtest/servio ==> servio.go function ServerFunc(etc,etc) Inside cli/server => main.go, main function, I import "modtest/servio" then write a call to |
fixed. please update tools and check. go get -u github.com/visualfc/gotools Windows/Linux: copy GOPATH/bin gotools and gocode to liteide/bin |
seems fixed to me. Thanks |
Hello @visualfc Installing liteide in /usr/local/bin makes things harder to have those deps inside of it. Would it be possible to make an option to specify GOPATH and thus use that path for those two binaries, if existing? |
Please answer these questions before submitting your issue. Thanks!
Please download LiteIDE latest version and test before submitting your issue. Thanks!
What version of LiteIDE are you using (LiteIDE About - Version and Build Qt Version)?
X34.1 (Qt 5.5.1)
What version of Go are you using (
go version
)?go version go1.11 linux/amd64
What operating system and processor architecture are you using(
go env
)?linux / amd64
What did you do?
Created a module-based project with several subpackages. For example package A with sub-package A1, and package B. A1 uses B.methodB()
If possible, provide a recipe for reproducing the error.
Right-click on "B.methodB()" and chose "Jump to declaration"
What did you expect to see?
Editor goes to package B, to the file containing func methodB()
What did you see instead?
Nothing happens. Problem just with packages inside module. Packages inside the /pkg/mod cache work.
The text was updated successfully, but these errors were encountered: