android - Guidance on refactoring complex dagger implementation -


our large android application makes extensive use of dagger - simplifies codebase , assists unit testing using robolectric. generally, pleased way works.

over time, numerous dagger modules have been developed providing object injections various aspects of application. approach feels fragmented unclear demarcation between modules. inevitably, same object has wound in multiple modules , multiple modules required satisfy @injects annotations in classes. combination of library=true , complete=false means missing out on compile time checking well. adding new objects module can tricky , feels if fighting dagger rather using it.

we have set of test modules provide mock objects duplicate many of issues in main app.

the time has come refactor our dagger implementation , clean of organic growth beginning hurt us. there preferred approach implementing dagger?

  • should place in 1 large module - 1 main app , 1 unit test?
  • should split existing modules down lots of tiny modules focused on function , include modules roll them feature level module?

any guidance based on experience welcome.


Comments

Popular posts from this blog

javascript - Jquery show_hide, what to add in order to make the page scroll to the bottom of the hidden field once button is clicked -

javascript - Highcharts multi-color line -

javascript - Enter key does not work in search box -