Decouple Account class from EF Core Identity #668
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to de-couple the EF Core identity framework from the Domain model. This way, we can re-use the Account class in the Core and Application layer, allowing us to tie user accounts to applications or other entities. Signed-off-by: Matthew Fisher <matt.fisher@fermyon.com>
bacongobbler
added
enhancement
|
dropping for now; let's revisit when we actually implement a permissions layer. |
1 similar comment
|
dropping for now; let's revisit when we actually implement a permissions layer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to de-couple the EF Core identity framework from the Domain model. This way, we can re-use the Account class in the Core and Application layer, allowing us to tie user accounts to other entities in Core.
closes #599.