h4. Update
I have done research for the work. Currently our SDK is implementing similar approach to Dagger2.
We spike that at the moment as part of the:
https://github.com/aerogear/aerogear-android-sdk/pull/2
h4. Moving to dagger
Moving to dagger is not possible at the moment:
- we do not have enough services like httpd
- current solution will require some refactoring to get that and this may interfere with current work we doing
h4. Migration
Migration will require replacing our current dependency mechanism with dagger.
We should create modules for http, logging, storage etc and make them available as top level application component.
I have spiked that aproach on sample application:
https://github.com/googlesamples/android-architecture-components/tree/master/GithubBrowserSample
Our core gradle module should export modules. To do that users will need to register core as part of their application.
[Dagger modules|https://raw.githubusercontent.com/codepath/android_guides/master/images/dagger_general.png]
|
|
