Components don't reset their received parameters during hot reload updates

[SteveSandersonMS]

It's a bit unusual to remove a parameter value that you're passing to a child component, but if you do, our upcoming hot-reload-refresh mechanism doesn't yet account for it.

Repro: In the default project template, in Index.razor, change this:

<SurveyPrompt Title="How is Blazor working for you?" />

... to this:

<SurveyPrompt />

No change will show up in the UI. This is because the existing SurveyPrompt instance already has a value for its Title property. Failing to supply a new value just means that the old one doesn't get overwritten.

Expected resolution

We can't control how all IComponent types deal with the removal of an incoming parameter value, but for ComponentBase at least, we can add some logic to SetParametersAsync that checks the IsHotReload flag and, if found, runs through some new code path to default-out all of its [Parameter] properties before receiving the new set from its parent.

Severity

Low. I don't think this is a common scenario at all.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[danroth27]

@mkArtakMSFT @SteveSandersonMS Can we reconsider this one for .NET 6? This issue was hit in vendor exploratory testing.