You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
I'm in the middle of refactoring our code base from using Roboguice and I've hit a problem I'm not sure how to solve in an elegant way. We have all these places where people on my team used @Inject to inject into fields on custom Views that were inflated via xml, and Roboguice was magically resolving these. Now I'm trying to deal with these using Dagger.
How do you deal with these in Dagger? I'd hate to grab the activity graph with something like:
@JakeWharton Which way has been used to greater success? I'd like to make sure I'm not bloating my unit tests to set up stuff, and since I'm using field injection (on Views) it forces Dagger into the mix which I'm really not digging. Not sure I have much choice otherwise as passing dependencies in a method would force me to inject them outside the View and pass them in which sort of sucks as well.
I'm in the middle of refactoring our code base from using Roboguice and I've hit a problem I'm not sure how to solve in an elegant way. We have all these places where people on my team used
@Inject
to inject into fields on custom Views that were inflated via xml, and Roboguice was magically resolving these. Now I'm trying to deal with these using Dagger.How do you deal with these in Dagger? I'd hate to grab the activity graph with something like:
that makes me feel all dirty inside.
The text was updated successfully, but these errors were encountered: