Is there a way to have an indicator referring to the interface that a function implements and to see where an interface is implemented?

[clauderoy790]

I decided to make the switch from GoLand to VS Code and I'm liking it a lot so far. One of the thing that I haven't found how to do yet is VS Code that is possible to do in GoLand is to have an indicator next to a function that implements an interface method that refers to the implemented interface as such:

Also having an indicator in the interface itself that refers to implementation of that same interface.

Does anyone know if there's an extension for that in VS Code? I know it's possible to go to implementations from the interface when you right click it -> Go to implementations and from the interface implementation it works as well, but having an indicator is super useful because you see it right away.

If it doesn't exist, does anyone know if it'd be difficult to make an extension for that? I've never made one, but I'd be 100% done for it!

Thanks for the help,

Claude

[hyangah]

If you run "Find All Implementations" from the struct type, vscode will show the list of interfaces the type implements.
If you run "Find All Implementations" from a method, vscode will show the list of corresponding interfaces.
This is not very intuitive but it looks like this was an attempt to fit Go-specific information in the general purpose LSP concept back then.
golang/go#35550

There is no visual indicator though.

[clauderoy790]

Makes sense, thanks for clarifying that out!

[guettli]

BTW, there is an issue about getting up-arrow/down-arrow on interfaces and methods implementing an interface (like Golang): golang/go#56695 - maybe it is coming soon!

[tony-sol]

So is this not planned as part of plugin at all?

[jcastilloa]

I agree, I was looking for the same thing. These are those small features that once you get used to them, you can't live without.
I would switch to VSCode if it had more convenient interface navigation and maybe I didn't need a microscope to interpret the source tree, which is another thing that I don't find very usable, but that's another topic :))