Bind interface to implementation without boilerplate

Sometimes, for architectural reasons, I have interfaces with only one concrete class implementing them. Writing @Provides methods for these cases can involve a lot of boilerplate, especially if the constructor has a lot of dependencies.

e.g.

@Provides
@ActivityScope
public FavouritesListContract.Presenter provideFavouritesListPresenter(FavouritesClient favouritesClient,
        SearchStorage searchStorage, SettingsStorage settingsStorage, GoogleAnalyticsHelper googleAnalyticsHelper) {
    return new FavouritesListPresenter(favouritesClient, searchStorage, settingsStorage, googleAnalyticsHelper);
}

As long as the concrete implementation has an @Inject constructor it ought to be possible to just bind the class to the interface.

My thinking is that the binding still belongs in a Module. Perhaps a list of bindings could be provided in the @Module annotation?

[gk5885]

Yes, we are working on a feature that will let you do exactly that.

In the meantime, if FavouritesListPresenter has an @Inject constructor, this formulation is equivalent and much more brief:

@Provides
@ActivityScope
public FavouritesListContract.Presenter provideFavouritesListPresenter(FavouritesListPresenter impl) {
    return impl;
}

[ronshapiro]

Dagger 2.4 has been released, check out @Binds!