Blazor identity Manage Profile (Index.razor)

[mnbob70]

    protected override async Task OnInitializedAsync()
    {
        Input ??= new();

        user = await UserManager.GetUserAsync(HttpContext.User);
        if (user is null)
        {
            RedirectManager.RedirectToInvalidUser(UserManager, HttpContext);
            return;
        }

        username = await UserManager.GetUserNameAsync(user);
        phoneNumber = await UserManager.GetPhoneNumberAsync(user);

        Input.PhoneNumber ??= phoneNumber;
    }

Why does OnInitializedAsync retrieve user but then proceed to call UserManager.GetUserNameAsync and UserManager.GetPhoneNumberAsync instead of just using the values assigned to user?

        username = user.UserName;
        phoneNumber = user.PhoneNumber;

I'm going to be adding some additional members to a custom User class for profile editing and noticed this code while working through the changes. I planned to just use the user members directly but now I'm wondering if I'm overlooking something and would need to implement additional Get...Async methods in my custom UserManager to match this implementation.

[vst121]

GetUserAsync() gives you the user entity, but Identity does not guarantee that all values should be read directly from it. UserManager.GetUserNameAsync() and GetPhoneNumberAsync() exist so stores can:

• compute values dynamically
• map them from non-standard storage
• apply normalization / indirection
• support custom user stores that don’t expose fields directly

In the default EF Core store, those methods do just return user.UserName and user.PhoneNumber, so your version works today. The template uses the UserManager methods to stay store-agnostic and future-proof.

For your custom user properties:

• If they’re simple scalar fields → read them directly from user
• Only add Get…Async methods if the value:
  • isn’t stored directly on the entity, or
  • needs special logic / indirection

So you’re not missing anything. The template is being conservative; your approach is perfectly fine for profile data on a custom ApplicationUser.