Open biegehydra opened 9 months ago
I have since realized that this is easily fixable by just putting the restriction that the user must click on the name of the component, e.g. with the cursor on "Foo" in \<Foo T="List
Then the algorithm is just move left to find beginning of tag, then move right to find a '/' , '>', space, or newline while capturing the component name.
The find component usages features fails to detect components under certain scenarios.
<Foo T="List<string>" />
<Foo SomeStringParam="@("<TEST>")" />
<Foo SomeListOfStringParam="new List<string>()" ></Foo>