Go to References - to where the component is used

[lukaszpolowczyk]

Is your feature request related to a problem? Please describe.
I have an active tab open with a *.svelte component file in VSCode.
I want to jump to all uses of this component.

Describe the solution you'd like.
With the tab with the *.svelte component file open in VSCode:

• right-click in any empty line of the file
• choose "Go to References" (or the special menuitem "Go to References for this svelte component")
• jumps to each use of this component (of course it bypasses the import from sections - it only shows the places of use).

Another option: Menuitem in the context menu of the *.svelte file in Expoler and in the context menu of the tab with the *.svelte file.

Describe alternatives you've considered.
Searching via search engine (Ctrl+Shift+F) and typing component name.
This is less convenient because you have to type it manually, and because it also searches the import from section and any other place with the same name as the component, but it should bypass those sections.

[dummdidumm]

I think omitting the import from-results would be wrong because you might want to find components where there's only an import but the component is no longer used, or you want to remove components from certain files but then forget to remove their imports because they are not listed. Apart from that this is a feature I think would be good.

[lukaszpolowczyk]

@dummdidumm How about we make a compromise:
If there is ONLY import from in the file and no uses, then Go to References could include that import from. But if there are uses, it's better to omit import from for that file, because it just litters the Go to References list.

Eventually a separate function, showing also import from as Find all References - a separate function would be better.

[dummdidumm]

If we do that, then the use case of deleting all occurences in certain files is still not solved in a good way (not shown in the references, therefore it's easier to forget to delete it). Furthermore, imports are shown for all other references as well, so not doing it for Svelte components would be non-standard. I therefore am still against removing them, and the little additional clutter is something I happily trade for this consistency.

[lukaszpolowczyk]

@dummdidumm This is true.
It pains my heart, but I have to agree that matching the standard is important.
So be it.

[Jojoshua]

This is exactly the feature I am needing as well. Anything I can do to help?

[Blankeos]

Found:
🪟 Ctrl (🍏 CMD ) + Shift + P: Svelte: Find Component References