Idea: Allow 'Goto declaration' when triggered on the import string to show the directory the package is in?

[Dima-369]

Very minor thing.

I realized that triggering 'Goto declaration' on the import statement shows all usages of the package, which is amazing! I then tried it on the string after and no information was given, so I thought if maybe the directory to the package could be shown in that tooltip? Or just jumping to the first source file in the package?

[obiwan87]

1. With no alias it works with the beginning of the import statement. There it finds the places where import is used. I couldn't find a way to tie a string literal to a declaration yet
2. The behavior you suggest was something I thought of. I will check how the Go IDE behaves

[obiwan87]

Ok, after some research I think I figured out the best practice:

• Aliases always find the usages within the file
• The path part opens the directory of the package in the project view
• If the path is outside the project, then it has to be added as external library in order for the "open directory" feature to work
• if the path is not an external library, do nothing

In order for this to work, first, we have to add the SDK path as external library

https://plugins.jetbrains.com/docs/intellij/workspace-model.html

[obiwan87]

This features has been implemented as described above :)

[Dima-369]

This features has been implemented as described above :)

Nice, works well!