Rule MA0115 - Unknown component parameter not working for third part packages about meziantou.analyzer

[meziantou]

The latest version should report unmatched pascal-case parameters

[meziantou]

The issue is that the MudBlazor component allows any attribute because the base component has the UserAttributes property

[Parameter(CaptureUnmatchedValues = true)]
public Dictionary<string, object?> UserAttributes { get; set; } = new Dictionary<string, object?>();

I wonder if the rule should detect attribute starting with an uppercase letter that doesn't match a property. Most html attribute are lowercase. Maybe it would be a better heuristic to support this case.

[gabephudson]

Thanks for looking into this! Yeah, many Blazor UI components will allow this so they can pass through standard/non-standard HTML attributes.

As you said, these are typically lowercase where component parameters are often uppercase (by convention). That sounds very reasonable to me, although it is not bullet proof.

Would love to be able to see these flagged in this case, even if it's a separate rule that can be disabled for other's that don't want it flagged. I think this will be needed for any UI Blazor frameworks (which is what many NuGet Blazor packages are).

[gabephudson]

I can confirm this change now highlights MA0115 for this library. This is extremely useful (don't know why it's not part of the standard warnings). Thank you so much for the quick tweak and this wonderful set of analyzers!

[NaserParhizkar]

I would like to use Blazor parameters with something like [] same as Angular to be sure when I change a parameter name in the future, I could trace problem by use of editor and by use of compile errors. I see, only Angular could recognize and throw error when a parameter name change, even React can not detect parameter name changes.

[meziantou]

@NaserParhizkar If this is a feature, can you open another issue? Also, could you give an example of the pattern you want the rule to support?

[NaserParhizkar]

@meziantou Your tools (Meziantou.Analyzer) is good and resolve my question, but unfortunately when I click on warning

message  'Severity	Code	Description	Project	File	Line	Suppression State	Details
Warning (active)	MA0115	The parameter 'name' does not exist on component 'BlazorApp23.Components.Test.MyTest' (https://github.com/meziantou/Meziantou.Analyzer/blob/main/docs/Rules/MA0115.md)	BlazorApp23	C:\Users\Asus\source\repos\BlazorApp23\BlazorApp23\obj\Debug\net8.0\Microsoft.CodeAnalysis.Razor.Compiler\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Components_Pages_Home_razor.g.cs	100		

I expect to redirect to page I used the component with wrong property name in order to correct it.

[meziantou]

I think this is a limitation of Roslyn. MA0115 analyze the code generated by Razor. So, it doesn't analyze the razor file but a cs file (e.g. Components_Pages_Home_razor.g.cs).
Razor uses the #line directive to do the mapping between the cs and razor file, but I don't know if Roslyn use it when double-clicking on the error.