Migrate to Latest version of Dagger

[JamesSmartCell]

Currently we are stuck on Dagger 2.22 - the latest version (as this issue is written) is 2.35.1 / 2.28.3

To upgrade you can go through this tutorial, as above 2.22 Dagger changes quite a bit:

https://proandroiddev.com/getting-started-with-dagger-2-27-on-android-by-example-8534f468175

After this refactor, the injection code should look a little less complex, and the effort to add a new Activity should be slightly less.

Things to watch out for:

some ViewModels serve multiple activities, for example:

    @ActivityScope
    @ContributesAndroidInjector(modules = TokenFunctionModule.class)
    abstract TokenFunctionActivity bindTokenFunctionActivity();

    @ActivityScope
    @ContributesAndroidInjector(modules = TokenFunctionModule.class)
    abstract FunctionActivity bindFunctionActivity();

    @ActivityScope
    @ContributesAndroidInjector(modules = TokenFunctionModule.class)
    abstract TokenDetailActivity bindTokenDetailActivity();

    @ActivityScope
    @ContributesAndroidInjector(modules = TokenFunctionModule.class)
    abstract TokenActivity bindTokenActivity();

This may be quite a big project - if you encounter difficulties please let me know.

[asif-finimble]

@JamesSmartCell, we need to use dagger-hilt right?

[asif-finimble]

Task Update Jan 19, Wednesday:

• Latest verison of Dagger is 2.40.5. It has Hilt for easier injection in Android.
• Migrated Dagger-android 2.2 to Dagger-hilt 2.40.5.

  Changes:

• @Component, @ContributesAndroidInjector, etc are removed.
• ViewModelFactories are not required in Hilt as they are auto generated. Therefore all modules for providing dependencies for ViewModelFactories are combined to a single module called ViewModelModule.
• AppComponent is not required as @HiltAndroidApp generates it.
• Unlike dagger, Hilt uses monolithic component system meaning all activities have components with same class definition, though the instances are different. More: https://dagger.dev/hilt/monolithic.html. Due to this we don't need to create separate modules for each activity. Any Module with @InstallIn(ActivityComponent.class) can provide dependencies to all activities.
• For injection, all activities and fragments are annotated with @AndroidEntryPoint.
  • ViewModels are annotated with @HiltViewModel and @Inject on constructor.
• No need to define binding for application context. Hilt provides @ApplicationContext to inject application context.

[asif-finimble]

References, guides & tutorials used:

• Migration guide: https://dagger.dev/hilt/migration-guide
• Baiscs:
  • https://dagger.dev/hilt/quick-start.html
  • https://dagger.dev/hilt/view-model.html
  • https://developer.android.com/training/dependency-injection/hilt-android

[asif-finimble]

Adding new Activity or Fragment & how to inject

• Annotate the Activity/Fragment with @AndroidEntryPoint. This will allow the activity/fragment to access dependencies from the components.
• Annotate the field or constructor with @Inject for injecting dependencies.
• Activities can access dependencies from ActivityComponent and its parent components ie modules with @InstallIn(SingletonComponent.class), @InstallIn(ActivityRetainedComponent.class) & @InstallIn(ActivityComponent.class).
• Fragments can access dependencies from above components in addition to FragmentComponent.

Injecting into ViewModels

• Annotate the ViewModel with @HiltViewModel.
• Annotate the field or constructor with @Inject.
• ViewModels can receive dependencies from Modules with @InstallIn(SingletonComponent.class), @InstallIn(ActivityRetainedComponent.class) & @InstallIn(ViewModelComponent.class).
• Define dependencies for ViewModels in ViewModelModule.

Injecting into Service(Android)

• Annotate Service class with AndroidEntryPoint and fields/constructor with @Inject.
• Define dependencies in ServiceModule.

Component Hierarchy: https://dagger.dev/hilt/components.html#component-lifetimes

[asif-finimble]

Task Update Jan 20:

• Migration Done. Tested major screens. Working fine.
• Pushed the Code.

@JamesSmartCell can you please test it on your end and let me know if I should make any changes?

[JamesSmartCell]

Thanks, I'll check it, it's this branch right:

https://github.com/AlphaWallet/alpha-wallet-android/tree/2321_migrate-dagger-to-latest

[asif-finimble]

Thanks, I'll check it, it's this branch right:

https://github.com/AlphaWallet/alpha-wallet-android/tree/2321_migrate-dagger-to-latest

Yes.