Lack of Intellisense Suggestions for Blazor Component Parameters in Rider, While Visual Studio Offers Them
Hello everyone,
I'm working on a Blazor project and using JetBrains Rider as my IDE. While attempting to set parameters for a custom Blazor component, I've noticed that Rider's Intellisense does not provide autocomplete suggestions for the available parameters of the component. However, when I try the same in Visual Studio, the Intellisense feature works as expected and gives me parameter suggestions.
The component in question is BlazorAndTailwind.Components.Pages.Components.Table, and the parameters I am trying to set include TableTitle, HideTableHead, and HideSearchbar.
Is this a known issue or limitation in Rider, or could this be due to some misconfiguration on my part? Any help would be appreciated!
EDIT: It's worth noting that I'm not using a class library for the components; everything is housed within a single project. I have also noticed that Rider has a very hard time finding newly created components as well. I have to type in the full path for it to understand that it is a component. Example: BlazorAndTailwind.Components.Pages.Components.Table
Please sign in to leave a comment.
Hi Jonas,
Thank you for your comment.
There are some known issues with Blazor component indexing/auto-complete features in our issue tracker:
RSRP-492485 Blazor custom component's parameter can't be resolved when wrapped inside an if statement.
RSRP-494494 False error in Blazor component attribute
RIDER-27167 Auto complete Blazor Parameters
If your situation differs from the above tickets, it would be great if you could help us demonstrate the issue in a sample project. I will then create a separate ticket to investigate the issue further. Thank you for your collaboration!
Regards,
Tao
Hey Tao Sun ,
The issues mentioned above are pretty much what I'm experiencing as well. Glad to hear you are aware of it.
Hi Jonas,
Thank you for your understanding. I hope my suggestions on using Blazor in Rider will be helpful to you.
Rider is always committed to providing users with the best .NET development experience. However, there are still many restrictions within the .NET SDK design, including the Hot Reload functionality we discussed before, which is not easy to resolve from our side.
If you encounter any issues in Blazor development, please don't hesitate to contact us, and we will do our best to help locate and resolve the problem. Thank you for your kindness and understanding!
Regards,
Tao
Hi Jonas Karlsson,
I checked the YouTrack tickets shared to you yesterday and some of them already closed.
Would you mind sharing a sample project that reproduce the issue with me? So that I can keep following up the issue with the symptoms.
Thanks for your collaboration.
Regards,
Tao
Hey Tao Sun ,
You know what, I've managed to figure it out now. I forgot to enter a "using statement" at the top. I'm so used to Rider helping me with that that I forgot about it.
As an example, I had to add:
@using ComponentTest.Pages.Componentsat the top so Rider would understand where to look for the component.