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 only skimmed through the source code, but I noticed that the UserDataStoreFactory and the RestApiImpl have a dependency on Android libraries. This appears to break the rule for the Clean Architecture Dependency Rule: "source code dependencies can only point inwards and nothing in an inner circle can know anything at all about something in an outer circle."
Is the Android Context used for the UserDataStoreFactory and could it be removed?
Is it possible to check connectivity from RestApi without dependency on Android libraries?
I am trying to find an architecture that I can write my core library that would interface with both mobile and web apps. I like the concepts of the Clean Architecture for this.
The text was updated successfully, but these errors were encountered:
anotherhale
changed the title
Data Layer with Android Dependency
Data Layer with Android Dependencies
Apr 3, 2015
The fact that data layer has dependencies with the android framework does not mean the rule is broken. Actually you need them otherwise I would not be able to fulfill the needs of that module.
I have only skimmed through the source code, but I noticed that the UserDataStoreFactory and the RestApiImpl have a dependency on Android libraries. This appears to break the rule for the Clean Architecture Dependency Rule: "source code dependencies can only point inwards and nothing in an inner circle can know anything at all about something in an outer circle."
Is the Android Context used for the UserDataStoreFactory and could it be removed?
Is it possible to check connectivity from RestApi without dependency on Android libraries?
I am trying to find an architecture that I can write my core library that would interface with both mobile and web apps. I like the concepts of the Clean Architecture for this.
The text was updated successfully, but these errors were encountered: