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
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.
Do you consider this to be an important principle?
If important, how would you refactor?
Thanks for any consideration.
The text was updated successfully, but these errors were encountered:
keithlemon
changed the title
Should the Entity class
Should the Entity Class Move to an Infrastructure Project?
Mar 17, 2018
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.
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.
Thanks for any consideration.
The text was updated successfully, but these errors were encountered: