Non-null parameters for Blazor components

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

If I declare a blazor/razor component to expect a non-null parameter value, like this:

[Parameter, EditorRequired]
public Season season { get; set; }

then I would expect there to be at least a warning if I were to pass it a possibly null-valued nullable variable like this:

Season? nullableSeason;
<Component season="nullableSeason" />

But there is no such warning in the current version of Visual Studio (Version: 18.0.0 Insiders [11109.219]), leaving a pretty big hole in nullability safety checking.

Can this be improved?

---

Original Comments

Feedback Bot on 10/14/2025, 01:27 AM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. You will hear from us in about a week on our next steps.

[javiercn]

Thanks for contacting us.

This can't be improved because parameters are set by the framework and bound directly from a dictionary structure. EditorRequired will make sure that the parameter is passed when passing parameters explicitly, but it can cover things like parameter splatting.

The [Parameter] type Property { get; set; } is not a convention of IComponent so the framework can't validate that the parameters are present at runtime.