Discussion: Expanding the find components usages functionality

[biegehydra]

I think being able to click on a component and find it's usages was a great start, but that only covers about half the use cases for when you want to find a component.

I don't know about everyone else, but most of the time I want to find a components usages it's because I am currently working on a new razor file that someone else created and I want to see how it's being used. I wouldn't have a component usage to click on in this scenario. In this case, I would have to first create a usage on the file I am working on then click on it to find usages. This is cumbersome.

I have 3 ideas.

• Contextual: If you right click on a line in a razor file without any component usages and then click "Find component usages", it will find the usages for the razor file that you are currently working on (instead of showing an error like it currently does).
• Solution Explorer: Show the "Find component usages" option when you right click on a .razor file in the solution explorer
• Input Field: Add a search input field on the Component Usages wpf component.

Or any combination of the above.

[EngstromJimmy]

This makes sense. I just implemented number 1.

[EngstromJimmy]

Let's add all of these before we release a new version