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 have a question regarding the Now in Android project.
It follows the Google App Architecture guidelines, and currently the data module uses api dependencies to expose the database and network modules transitively. The issue is that even when a feature module only depends on the data module, it can still directly access data models from the database or network modules (e.g., NetworkNewsResource).
Is this the intended structure?
Personally, I feel that this blurs the boundaries between layers, which undermines the purpose of separating the architecture. What are your thoughts on this?
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
Uh oh!
There was an error while loading. Please reload this page.
-
I have a question regarding the Now in Android project.
It follows the Google App Architecture guidelines, and currently the data module uses api dependencies to expose the database and network modules transitively. The issue is that even when a feature module only depends on the data module, it can still directly access data models from the database or network modules (e.g., NetworkNewsResource).
Is this the intended structure?
Personally, I feel that this blurs the boundaries between layers, which undermines the purpose of separating the architecture. What are your thoughts on this?
Beta Was this translation helpful? Give feedback.
All reactions