RC2 Blazor Web App template nits and inconsistencies

[rogihee]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

A few small nits / inconsistencies after creating a new "Blazor Web App" template with the following options

1. ManageNavMenu.razor in Components\Layout has superfluous ; that can be omitted:
   

2. In the same file, the private component variable is prefixed with an underscore:
   
   However, in the Weather.razor the underscore-less convention is used:
   
   My personal coding style is: If it is used in the razor template, use a private property, else a private variable with underscore. That way I can distinct private vars only for the code section and vars used in the render template.
   RegisterConfirmation.razor is then inconsistent again with no explicit private modifier and no underscore. Same in ResetPassword.razor
   

3. StatusMessage.razor has logic in the razor template. I would avoid doing that and move the code block at the top into OnParametersSet override.
   

4. In a couple of places OnInitialized sets a Parameter, but OnParametersSet will always override that, I think.
   
   Also in ExternalLoginPicker.razor, LoginWith2fa.razor, LoginWithRecoveryCode.

5. Unused using and inject in Index.razor in Account/Manage and in PersonalData.razor, Register.razor:
   
   As a side note, I usually move all the usings to the _Imports.razor file so the component files are short and concise.

6. Two properties in the Error.razor can be made private:
   

Expected Behavior

Running the template produces concise, correct code

Steps To Reproduce

Run the template as demonstrated above and inspect all the files

Exceptions (if any)

No response

.NET Version

8.0.100-rc.2.23502.2

Anything else?

17.8 Preview 3

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. 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.

[halter73]

Thank you for reporting these issues! It's all really good feedback. Between #51134 and #51497, all 6 issues you highlight should be addressed.

[rogihee]

Thanks for listening en fixing!