Duplicate binding but no binding defined in component about dagger HOT 4 CLOSED

Why is it bound by @Component.modules in ChildScope if the @Provides @ParentScoped has different scope from the component?

By adding a module to @Component.modules() it means every @Provides/@Binds method in that module is installed in that component. There's no way to tell Dagger to only install certain @Provides methods and not others.

Doesn't docs say components cant have differently scoped providers in them?

That's correct. Normally, if you try to install a module in a component and one of its @Provides methods has the wrong scope then Dagger will report an error about it. I think the only reason you aren't seeing that here is because Dagger checks for duplicate bindings first, so it's reporting that error instead.

from dagger.

i want to group stuff together by functionality in modules throughout cross-cutting concerns components from different level of scoping. Is there an alternative way of doing it without requiring me to split into module-per-scope?

No, you will need to split the provides methods into two separate modules.

is there a simple explanation why is String a being bound multiple times? I didn't bind it anywhere in ChildScope.

It's bound once via the @Component.modules = SharedModule.class and again via the @Component.dependencies = ParentScope.class.

from dagger.

Why is it bound by @Component.modules in ChildScope if the @Provides @ParentScoped has different scope from the component? Doesn't docs say components cant have differently scoped providers in them? It should probably try to use binding from parent if scope doesn't match, no?

from dagger.

Thanks for the insightful comment. Appreciate it. I'll use separate modules then 😁

from dagger.