Paul Woitaschek11/19/2018, 5:27 PM
Paul Woitaschek11/21/2018, 2:02 PM
. Now this recipe component needs to depend on dependencies from my
. So far - fine, no problems. Now in my App I want to show a
, so my app needs to have a dependency on the
dagger module. How do you overcome this circularity?
not depend on the
but rather expose all it's dependencies through a `bindsInstance' method. But there are like 10 of them so this scales not too well.
David11/21/2018, 2:22 PM
you allude to) but in the cases where I am modularising I am never binding anything more than
to a child module as part of the
(gradle) modules have a dependency on the this base component?
Paul Woitaschek11/21/2018, 2:30 PM
I suspect you are going to say analytics, retrofit, okhttp and many other “true” read-only singletons.
David11/21/2018, 2:31 PM
a dependency on
) then you’d need to work as subcomponents do. If on the other hand you “push down” (notice ‘dumb’ modules that contain POJO & POKOS in
in particular are right at the bottom of the graph) then you can use the
construct to control what is exposed to consumer modules.
Paul Woitaschek11/21/2018, 2:43 PM
David11/21/2018, 2:49 PM