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
Hi, one question related to domain project/module...
Can you explain a little bit more what is a reason that use-cases and domain logic are in
the same module, shouldn't it be more appropriate to separate use-cases to application layer
and domain entities with all their logic to domain layer... This way the domain layer is
shareable as enterprise-wide rules....
Domain layer is not supposed to contain enterprise-wide rules, this is embedded in its very name itself.
Usual Android approach to Clean Architecture is simplified comparing to the original concept as generally you don't have a set of business logic that many applications need to share.
But, of course, you can incorporate such a layer in a separate module if you need to.
Hi, one question related to domain project/module...
Can you explain a little bit more what is a reason that use-cases and domain logic are in
the same module, shouldn't it be more appropriate to separate use-cases to application layer
and domain entities with all their logic to domain layer... This way the domain layer is
shareable as enterprise-wide rules....
The text was updated successfully, but these errors were encountered: