dagger-2

问题 I'm using Dagger 2 with retrofit2 library while using MVP. Everything went well till I tried to integrate another service (basically I tried to initialize another retrofit object to another service). I followed this answer but without any success. Every time I'm getting an errors that each of my fragments and application classes don't seem to recognize the component classes. error: cannot find symbol class DaggerApplicationComponent error: cannot find symbol class DaggerEpisodeComponent Code

问题 Considering modules are all shared among one-another through the Dagger1 specification of complete=false, library=true , you can receive the elements provided by the @Provides methods through a constructor parameter, like so. public class GetUserForUsernameTaskImpl implements GetUserForUsernameTask { public static final String TAG = GetUserForUsernameTaskImpl.class.getSimpleName(); private Realm realm; private UserRepository userRepository; public GetUserForUsernameTaskImpl(Realm realm,

问题 i'm trying to use Dagger 2 into my apps but i'm having some problems regarding the entities repository and i haven't figured it out what i'm missing. Here is my Application Component: @Singleton @Component( modules = { AndroidModule.class, RepositoryModule.class } ) public interface ApplicationComponent { void inject(AndroidApplication app); IDependenceyRepository dependencyRepository(); } My modules: @Module public class RepositoryModule { @Provides @Singleton IDependenceyRepository

问题 Last week, while implementing Dagger in my current Kotlin MVP project, I was testing it on oldy phone with KitKat 4.4.2 (yep, it still supports all major material features and stuff :)) due to primary phone's maintenance. So that week I was having typical issues rather than something unusual and fixed them more or less quickly by investigating provided errors. At long last, code compiled, current project version was built without issues and ran without major bugs on KitKat with UI interacting

问题 I have a scoped dependency in my Activity and I want to test that activity with some mocks. I have read about different approach that suggest to replace Application component with a test component during the test, but what I want is to replace the Activity component. For example, I want to test the Activity against mock presenter in my MVP setup. I believe that replacing component by calling setComponent() on Activity will not work, because Activity dependencies already injected via field

问题 I have this Dagger 2 configuration: AppComponent.kt @Singleton @Component( modules = [ AndroidSupportInjectionModule::class, AppModule::class, ActivityBindingModule::class, ] ) interface AppComponent : AndroidInjector<AppApplication> { @Component.Builder abstract class Builder : AndroidInjector.Builder<AppApplication>() } ActivityBindingModule.kt @Module abstract class ActivityBindingModule { @ActivityScoped @ContributesAndroidInjector( modules = [ MainActivityModule::class, FragmentModule:

问题 I have this Dagger 2 configuration: AppComponent.kt @Singleton @Component( modules = [ AndroidSupportInjectionModule::class, AppModule::class, ActivityBindingModule::class, ] ) interface AppComponent : AndroidInjector<AppApplication> { @Component.Builder abstract class Builder : AndroidInjector.Builder<AppApplication>() } ActivityBindingModule.kt @Module abstract class ActivityBindingModule { @ActivityScoped @ContributesAndroidInjector( modules = [ MainActivityModule::class, FragmentModule:

问题 At this point, my understanding of Dependency Injection (DI) is only from this article. I'm interested to try, but I just need to clarify some things: Many refer DI as a tool to reduce boilerplate code. But according to that tutorial, the setup of Dagger 2 tends to create even more classes for configuration (module and component). I have not tried it, but by the looks of it, it isn't reducing the code, it is just splitting them so the main class can look tidier. Am I wrong on this one?

问题 At this point, my understanding of Dependency Injection (DI) is only from this article. I'm interested to try, but I just need to clarify some things: Many refer DI as a tool to reduce boilerplate code. But according to that tutorial, the setup of Dagger 2 tends to create even more classes for configuration (module and component). I have not tried it, but by the looks of it, it isn't reducing the code, it is just splitting them so the main class can look tidier. Am I wrong on this one?

问题 I have this Dagger module. I want to understand the generated code so I can verify that my Dagger configuration is optimal. @Module public class TypefaceModule { @Provides @Singleton @Named("Roboto Light") static Typeface provideRobotoLight(AssetManager assets) { return Typeface.createFromAsset(assets, "fonts/Roboto-Light.ttf"); } } Here's the generated code (Dagger 2.14.1): public final class TypefaceModule_ProvideRobotoLightFactory implements Factory<Typeface> { private final Provider