Skip to content

Better package distinction for sources in completion #1900

@dlsniper

Description

@dlsniper

Hi,

I've noticed that there are two packages that provide the same function with the same signature.
One is from the SDK and one is from a third party package (Azure SDK for Go in this case and I've had issues where other packages have an fmt package which has the same Printf function and so on).

In the completion suggestions things look like this:
snapshot86

As you can see, there's going to be a lot of confusion as to what one should use in this case. Given the fact that the plugin can't determine which of the versions is required, the use should be able to quickly decide which is the targeted package.

One obvious option would be to show the SDK version a bit different but in cases where the same package name and function signatures are presented from multiple different packages in the GOPATH this would be only partially helpful.

Once the package is imported, currently the plugin will work properly and produce suggestions only from the imported package.

What do you think?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions