Is it possible in Dagger to do something like the following:
public abstract class Presenter<T extends BaseView> {
@Inject T mView;
public void showLoadingIndicator() {
mView.showLoading();
}
}
(example module)
public class MyModule {
private MyView mView; //extends BaseView
public MyModule(MyView view) {
mView = view;
}
@Provides
public BaseView provideView() {
return mView;
}
}
And then create an object graph with the module above and inject the view into the presenter?
My attempts have not worked (usually get "unknown class 'T'" sort of errors). I'm not sure if my configuration is wrong or if this is unsupported functionality.
There's a simple/obvious workaround to achieve the same thing, depending on what the rest of your code looks like.
By not using field injection to initialize the mView
field of the base presenter, you could just pass it into the constructor, and let the Module provide it, like:
public abstract class Presenter<T extends BaseView> {
private final T mView;
public Presenter(T view) {
mView = view;
}
public void showLoadingIndicator() {
mView.showLoading();
}
}
assuming it's used like this:
public class MainPresenter extends Presenter<MainActivity> {
public MainPresenter(MainActivity view) {
super(view);
}
}
and the module creates the presenter and passes the view to it:
@Module(injects = MainActivity.class)
public class MainModule {
private final MainActivity mMainActivity;
public MainModule(MainActivity mainActivity) {
mMainActivity = mainActivity;
}
@Provides
MainPresenter mainPresenter() {
return new MainPresenter(mMainActivity);
}
}
I prefer this anyway, because I prefer constructor injection over field injection (except on the objects not created by Dagger such as the activity or fragment level of course, where we can't avoid @Inject
).
code here