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.