-
Notifications
You must be signed in to change notification settings - Fork 299
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
Allow to define Onion Architecture without Domain Services #271
Comments
pszymczyk
changed the title
Allow to define Onion Architecture without domain services
Allow to define Onion Architecture without Domain Services
Nov 28, 2019
hankem
added a commit
that referenced
this issue
Dec 2, 2019
Signed-off-by: Manfred Hanke <[email protected]>
codecholeric
pushed a commit
that referenced
this issue
Jan 9, 2020
Signed-off-by: Manfred Hanke <[email protected]>
codecholeric
added a commit
that referenced
this issue
Jan 9, 2020
Resolved by #273 |
codecholeric
pushed a commit
that referenced
this issue
Feb 21, 2021
Signed-off-by: Manfred Hanke <[email protected]>
codecholeric
added a commit
that referenced
this issue
Feb 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I've just bump ArchUnit to 0.12.0 and one of my tests failed. It's because I have a module which has no Domain Services - only Application Services and Domain Model components. From my understanding this situation is totally ok and still consistent with all Onion Architecture principles, that's why in my opinion Domain Services layer should be an optional layer. What it's your point of view? If you agree I can proceed with Pull Request solving this issue.
The text was updated successfully, but these errors were encountered: