Provide instance without interface using Dagger

Content Index :

Provide instance without interface using Dagger
Dagger 2 - two provides method that provide same interface
Dagger 2: Provide same instance between multiple Component with same Scope on different library modules
Can dagger provide different implementations of the interface, depending on requested type?
(Dagger 2) Provide same instance for different types in MVP
Dagger can't inject a parameter of type interface on a ViewModel's constructor using Dagger Android

Provide instance without interface using Dagger

Tag : kotlin , By : James B

Date : November 28 2020, 04:01 AM

it fixes the issue When you use constructor injection Dagger can construct the object for you and you're already using Dagger to create ModelImpl to use it as a binding for Model in your example!

class ModelImpl @Inject constructor(...): Model{}

@Provides
fun model(inst: ModelImpl): Model = inst

// somewhere else...
// both variants would work!
@Inject lateinit var modelImpl : ModelImpl
@Inject lateinit var model : Model

class ModelImpl @Inject constructor(...)

// somewhere else...
@Inject lateinit var model : ModelImpl

// foo and bar can both be constructor injected
class Foo @Inject constructor()
class BarImpl @Inject constructor(val foo : Foo) : Bar

@Module
interface BarModule() {
  @Binds  // you should prefer Binds over Provides if you don't need initialization
  // barImpl can be constructor injected, so it can be requested/bound to its interface here
  fun bindBar(bar : BarImpl) : Bar
}

@Component(modules = BarModule::class)
interface BarComponent {
  fun getBar() : Bar // returns barImpl due to binding
}

@Inject lateinit var bar : BarImpl // but we could as well use the implementation directly
@Inject lateinit var bar : Foo // or just foo

Comments

No Comments Right Now !

Boards Message :

You Must Login Or Sign Up to Add Your Comments .

Share :

Tags :

Provide instance without interface using Dagger , Dagger 2 - two provides method that provide same interface , (Dagger 2) Provide same instance for different types in MVP , Can dagger provide different implementations of the interface , depending on requested type , interface extends interface java ,

Dagger 2 - two provides method that provide same interface

Tag : java , By : Raghu

Date : March 29 2020, 07:55 AM

this will help I recently post the answer to a question like this in this post :
Dagger 2 : error while getting a multiple instances of same object with @Named

@Module
public class ApplicationModule {
private Shape rec;
private Shape circle;

public ApplicationModule() {
    rec = new Rectangle();
    circle= new Circle ();
}

@Provides
 @Named("rect")
public Shape provideRectangle() {
    return rec ;
}

@Provides
 @Named("circle")
public Shape provideCircle() {
    return circle;
}

@Inject
@Named("rect")
 Shape objRect;

@field:[Inject Named("rect")]
lateinit var objRect: Shape

Dagger 2: Provide same instance between multiple Component with same Scope on different library modules

Tag : java , By : Zinovate

Date : March 29 2020, 07:55 AM

Any of those help Remove the injection sites from your CoreComponent - it now has the sole function of exposing the binding for CoreRepository to its dependent components:

@Singleton
@Component(modules = {CoreModule.class})
public interface CoreComponent {
    CoreRepository coreRepository();
}

public class MyApplication extends Application {
    private final CoreComponent coreComponent;

    @Override
    public void onCreate() {
        super.onCreate();
        coreComponent = DaggerCoreComponent
                            .coreModule(new CoreModule())
                            .build();
    }

    public static CoreComponent getCoreComponent(Context context) {
        return ((MyApplication) context.getApplicationContext()).coreComponent;
    }
}

@Scope
@Retention(RetentionPolicy.RUNTIME) public @interface PerActivity {}

@PerActivity
@Component(dependencies = {CoreComponent.class})
public interface ActivityComponent {
    void inject(FooActivity activity);

    void inject(BarActivity activity);
}

public class FooActivity extends AppCompatActivity {
        @Inject
        public CoreRepository repo;

        @Override
        protected void onCreate(@Nullable Bundle savedInstanceState) {
            super.onCreate(savedInstanceState);
            CoreComponent coreComponent = MyApplication.getCoreComponent(this);
            DaggerActivityComponent.builder()
                .coreComponent(coreComponent)
                .build()
                .inject(this);
        }
    }
}

Can dagger provide different implementations of the interface, depending on requested type?

Tag : development , By : mediafarm

Date : March 29 2020, 07:55 AM

it should still fix some issue This really depends on what you are trying to accomplish. You have 2 basic setups, whether you want to access your different implementations at once, or just want to supply one.
Access them at the same time / within the same scope

@Binds
@Qualifier("twitter")
Api provideApi(TwitterApi api);

@Inject @Qualifier("twitter") Api api;

@Component
interface ApiComponent {
  Api api();

  @Component.Builder
  interface Builder {
    @BindsInstance Builder api(Api api);
    ApiComponent build();
  }
}

(Dagger 2) Provide same instance for different types in MVP

Tag : android , By : 22.

Date : March 29 2020, 07:55 AM

I think the issue was by ths following , You can use constructor injection along with the @Binds annotation in your module to achieve this. Simply add a constructor and annotate it with @Inject in MyView. You can then mark MyView as @Singleton so that the same instance is used everywhere(assuming the component is also scoped with @Singleton).

@Singleton
class MyView extends MyAbstractView implements MyViewContract {
    @Inject
    public MyView() {}
}

@Module
abstract class MyModule {
    @Binds
    abstract MyInterface provideMyInterface(MyView myView);

    @Binds
    abstract MyViewContract provideMyViewContract(MyView myView);
}

Dagger can't inject a parameter of type interface on a ViewModel's constructor using Dagger Android

Tag : android , By : geo

Date : March 29 2020, 07:55 AM

wish of those help Solved the issue. Using a generic view model factory found in this Github issue:
https://github.com/google/dagger/issues/1273#issuecomment-447997439