You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 11, 2023. It is now read-only.
Something that is missing from this chapter is how to map the application user to tables in the database. For example, how do you add a property to the event examples that shows which user created the event. This is a scenario the students almost always run into on their projects.
Another thing the users run into is how to change from always displaying the email address as the user and instead collect the user's name. This prevents all other users from seeing everyone's email address.
Something that is missing from this chapter is how to map the application user to tables in the database. For example, how do you add a property to the event examples that shows which user created the event. This is a scenario the students almost always run into on their projects.
Another thing the users run into is how to change from always displaying the email address as the user and instead collect the user's name. This prevents all other users from seeing everyone's email address.
I cover this scenario here: https://medium.com/@scottkuhl/extending-asp-net-core-2-2-identity-management-c3cc657cc448
The text was updated successfully, but these errors were encountered: