Dagger 2: nested dependencies with same arguments in Module

Question

I have the following classes

    public class X {

    @Inject
    public X(B b){}

    }


    public class A {

    @Inject
    public A(B b){}

    }

    public class B {

    @Inject
    public B(String c){}

    }



    public abstract AppModule {

    @Binds
    abstract A bindA(A a);


    @Binds
    abstract B bindB(B a);

    @Provide
    static String stringForX(){
    return "oneX";
    }

    @Provide
    static String stringForA(){
    return "twoA";
    }

    }

Now B is injected into A and X. But the instance of B to be injected in X and A has to be internally injected with different Strings (stringForX() and stringForA(), respectively) How can i achieve this? I know @Named could be used but i am not sure how exactly in this particular case since B is common amongst them.

Thanks

use @Named https://stackoverflow.com/questions/18099909/dagger-inject-named-strings — Saurabh, Jul 19 '18 at 05:04
actually there is a small problem in using @Named. Updating the question. — Sunny, Jul 19 '18 at 05:07
well then i guess you have to manually provide 2 instances of B from module using @Named on those(instances of B). — Saurabh, Jul 19 '18 at 05:12

score 0 · Accepted Answer · answered Jul 19 '18 at 05:23

you have to manually provide 2 instances of B from module using @Named on those(instances of B).

example:

public class X {
  @Inject
   public X(@Named("b1") B b){}

}


public class A {

@Inject
public A(@Named("b2") B b){}

}

public class B {

public B(String c){}

}



public abstract AppModule {

@Binds
abstract A bindA(A a);


@Binds
abstract B bindB(B a);

@Provides()
@Named("1")
static String stringForX() {
    return "oneX";
}

@Provides
@Named("2")
static String stringForA() {
    return "twoA";
}

@Provides
@Named("b1")
B provideB1(@Named("1") String s) {
    return new B(s);
}

@Provides
@Named("b2")
B provideB2(@Named("2") String s) {
    return new B(s);
}

}

if it has to be done manually then do we need @Binds abstract B bindB(B a); any more? — Sunny, Jul 19 '18 at 05:25

Dagger 2: nested dependencies with same arguments in Module

1 Answers1