Skip to content
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

Should the Entity Class Move to an Infrastructure Project? #2

Open
keithlemon opened this issue Mar 17, 2018 · 1 comment
Open

Should the Entity Class Move to an Infrastructure Project? #2

keithlemon opened this issue Mar 17, 2018 · 1 comment

Comments

@keithlemon
Copy link

I wanted to see if there has been any thought with getting the Entity class outside of the Logic project? I ask as I have written many anemic applications in my life and one of the principles of the Onion architecture that I liked/followed was to try to keep infrastructure knowledge out of the Logic/Core project.

  1. Do you consider this to be an important principle?
  2. If important, how would you refactor?

Thanks for any consideration.

@keithlemon keithlemon changed the title Should the Entity class Should the Entity Class Move to an Infrastructure Project? Mar 17, 2018
@vkhorikov
Copy link
Owner

I saw others doing this but I personally don't see any value in introducing an additional project for Infrastructure when you work on a single bounded context. If there are more than one, then yes, it is valuable to extract common bits out to avoid duplication. Otherwise, it doesn't play well with YAGNI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants