Architecture-samples: [todo-mvp-dagger] - Setting Modules and Fragments for all Activities/Fragment
Hi,
Is there any reason for using a module and a component for every activity/fragment?
One explanation would be to prevent unintended usage of some classes, but does it worth it?
Thank you
ivandrag
>All comments
As an app grows it is nice to have the separation of dependencies for each UI elemnent. We are currently migrating to the new Dagger-Android constructs which will auto generate the subcomponents for each activity and fragment. While you may not need it in every app, we wanted to show what a setup looks like that has a separate module for each activity. Feel free to share an ActivityModule or a FragmentModule between many activities or fragments if you are not managing many dependencies that differ.
digitalbuddha
on 16 Aug 2017
👍3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
BeQuietLee
路
3Comments
ghost
路
3Comments
DharitParmar
路
6Comments
jchesterisidoro
路
3Comments
ialmetwally
路
5Comments
Most helpful comment
As an app grows it is nice to have the separation of dependencies for each UI elemnent. We are currently migrating to the new Dagger-Android constructs which will auto generate the subcomponents for each activity and fragment. While you may not need it in every app, we wanted to show what a setup looks like that has a separate module for each activity. Feel free to share an
ActivityModuleor aFragmentModulebetween many activities or fragments if you are not managing many dependencies that differ.