-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix BlazorServer Identity templates #25456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jmprieur
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @JunTaoLuo
|
A few notes for reviewers:
If my understanding is correct, I'm very concerned that this issue wasn't caught earlier
|
javiercn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jmprieur
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Since areas is only used in the IndividualLocalAuth case, maybe just the content of content/BlazorServerWeb-CSharp/Areas/Identity/Pages/Shared/_LoginPartial.cshtml with the content you've proposed for .../content/BlazorServerWeb-CSharp/Areas/Identity/Pages/Shared/_LoginPartial.Identity.cshtml would work?
|
@jmprieur you're absolutely right, It didn't occur to me that we don't need the _LoginPartial.OrgAuth.cshtml at all and I took the recommendation in the issue too literally. However, I'd like to address that for rc2 instead of re-triggering the CI checks again since there's a chance they might not complete before the 10AM deadline. Given the current code is correct but just more verbose than necessary, I'd like to get this change merged as-is. |
|
Approved for RC1 if merged before 10am Pacific on 2020-09-01. |
|
That sounds good to me, @JunTaoLuo |
jmprieur
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Tested
| @using Microsoft.AspNetCore.Components.Forms | ||
| @using Microsoft.AspNetCore.Components.Routing | ||
| @using Microsoft.AspNetCore.Components.Web | ||
| @using Microsoft.AspNetCore.Components.Web.Virtualization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this added in the first place? FYI, I discussed this a little more in #25456 (comment).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Virtualization isn't wasm specific, it's part of the core component experience: https://github.com/dotnet/aspnetcore/blob/master/src/Components/Web/src/Virtualization/Virtualize.cs#L12-L18.
It's weird that you're seeing the error. Perhaps you are using an an old targeting pack?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I believe the template is fine here and this is some environment-related issue. I see this PR is already merged but we should consider bringing it back in another PR. Perhaps @MackinnonBuck can resolve this in his virtualization improvements PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm making a followup PR to this one to rc2 so I'll do it there. Can one of you help me figure out why I was running into the error during verification?


Fixes #25353