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
And I know the position of repository interface is domain.
Google Android team introduced repository pattern. And this positioned "repository interface" at data layer.
Also Google Android team sad the domain layer is optional.
It makes me confusing a little.
("Now In Android" project also positions the repository interface at data layer.)
If I want use "domain layer" for some feature and modularaization it, it can't be test without dependency with data layer. And If the data layer changed so repository interface changed, useCase also must be changed.
How your team think about the Repository interface position?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
https://betterprogramming.pub/the-real-clean-architecture-in-android-part-1-s-o-l-i-d-6a661b103451
Above site introduced clean architecture.
And I know the position of repository interface is domain.
Google Android team introduced repository pattern. And this positioned "repository interface" at data layer.
Also Google Android team sad the domain layer is optional.
It makes me confusing a little.
("Now In Android" project also positions the repository interface at data layer.)
If I want use "domain layer" for some feature and modularaization it, it can't be test without dependency with data layer. And If the data layer changed so repository interface changed, useCase also must be changed.
How your team think about the Repository interface position?
Beta Was this translation helpful? Give feedback.
All reactions