Erroneous `////` in default URL for a blazorwasm template parameter

[jdmallen]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

This came up previously with an appsettings.json file, but I noticed it while exploring the parameters for the blazorwasm template, and I don't think that's been addressed yet.

It appears to me that this was unintentional. I have a fork and branch at the ready for a PR to fix this issue available here.

Expected Behavior

I expected a correct and valid URL format to be supplied as a default value that clearly requires one.

Steps To Reproduce

Repro:

1. Install latest .NET SDK (Host: 6.0.10, SDK: 6.0.402 as of this issue)
2. Execute dotnet new blazorwasm -h
3. Scroll down to parameter --aad-b2c-instance
4. Note the "Default" value of https:////aadB2CInstance.b2clogin.com/ verbatim and compare it to other default values on the screen.

Exceptions (if any)

No response

.NET Version

6.0.402

Anything else?

It's also worth noting that there's a similar issue with the "replaces" value at this line, but since it has a "defaultValue" also configured, the URL with the //// is not rendered to screen. I can fix that one, too, if you like, but figured I'd keep the commit focused.

Thanks for contacting us.
We're moving this issue to the .NET 8 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.

[jdmallen]

Because it's not immediately obvious that this is a bug in our framework

Have I not demonstrated clearly that it's a bug in the framework? It seems pretty obvious to me since it's writing a clearly malformed URL to a user interface, and it's easily reproducible. This seems a strange way to address issues, by automatically questioning a bug report's validity with a bot without any apparent human review.

so that the team can focus on more important and high impact issues.

I completely understand that this is low priority. Please bear in mind I've already fixed it and it's a single line of code to review. It should be low-hanging fruit, should you all choose to merge it into .NET 8.

I will not further bother the team about this. Thanks for your time.

[TanayParikh]

Due to

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Server/appsettings.json

Line 17 in 1e5fc75

// "Instance": "https:////aadB2CInstance.b2clogin.com/",

and

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Client/wwwroot/appsettings.json

Line 10 in 52eff90

// "Authority": "https:////aadB2CInstance.b2clogin.com/qualified.domain.name/MySignUpSignInPolicyId",

I believe we'll still need

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/.template.config/template.json

Line 375 in 25b4171

"replaces": "https:////aadB2CInstance.b2clogin.com/",

as-is, however, I think we should be able to resolve this by adding a default value of https://aadB2CInstance.b2clogin.com/ as we do here:

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/.template.config/template.json

Line 388 in 25b4171

"defaultValue": "https://login.microsoftonline.com/",

cc/ @javiercn who's the SME in this area, in case he has any considerations. @jdmallen feel free to put up a PR for this and we'd be happy to review.

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.