x/tools/gopls: Auto-make-up when calling public method or value after press '.' #44450
On the case you want to build a new project when there exists old projects, using GOPATH, Every outer-package public method can be well auto-make-up after press '.'
But now using gomodule, It can hardly auto-make-up method name unless I'm aware of what I want to import, then first go get it and then use it. This is too bad!
The text was updated successfully, but these errors were encountered:
If you can share a specific example of this issue, please do so. Please also take a look at our troubleshooting guide and attach your
When I take response to many projects, and now I want to start a new project.
In the past using GOPATH, starting a new project is just convenient because all packages can be well completed by gopls because all these normal packages're already in GOPATH as old project have downloaded them and share them.
Now using GOMODULE, even if I've hold many existed projects, when I start a new app project, I still need to consider which package I should go get first and then I can using gopls to auto completed its dot tip. I hope there exists a scheme that gopls can make-up a package that I use it in my new project in the first time(that it's just not go get yet), it can privilagedly refer to a package's newest version locally.
then, I want to start a new app5. At the first moment,
Then I press
At this time , gopls should refer to existed versions of gin where old existed projects just fullfill it. They're:
Gopls counts a latest version of gin and then choose v1.4.0 to finish its dot tip completion.
Then I got tip:
Emmm, I've asked my mates this situation. They ask me back:
How auto-completion knows which version of gin to pick?
Should this supported by IDE not go chain?
I'm also comfused of this!