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 Mar 10, 2024. It is now read-only.
What's the best practice for adding simple CRUD to this? Is the dbContext reusable for storing data other than the auth related stuff, or should it be done entirely separately?
The text was updated successfully, but these errors were encountered:
Yes, of course it is. Just add some DbSet properties to the dbcontext and then add a migration. It just already contains some default user tables for Identity.
Yes, of course it is. Just add some DbSet properties to the dbcontext and then add a migration. It just already contains some default user tables for Identity.
Thank you! It looks like API scaffolding will even do some of that lifting.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What's the best practice for adding simple CRUD to this? Is the dbContext reusable for storing data other than the auth related stuff, or should it be done entirely separately?
The text was updated successfully, but these errors were encountered: