in dagger, can a module say "single instance per whatever component this module gets attached to,"?

Maybe just use

@Reusable

?

Uhm never heard of it

you can keep it unscoped, if you meant you need a separate instance for every dependent class scratch that, just saw your other message

Well easiest would be to imagine say FooManager, and in AppA it needs to be app scoped, and in AppB it needs to be user scoped

but question is how to have 1 instance

it’s not guaranteed however

yes, it’s not guaranteed

Reusable from what I read can be destroyed, so its just sort of a cache

but (sub)component also can be destroyed

I want something sort of like

class FooModule {
    val fooManager by lazy { .. }
}

you can now attach this anywhere, in a daggerless world

attach?

to any component graph

you want to cache on level of module?

well, yea, so Ill end up with 2 exact same module definitions per app, which is stupid

if you could share scopes across app it would be possible. I doubt you need a totally different scope in each app. Anyway if you are working with multiple apps the instances won’t be shared anyway, you could just use

@Singleton

where, across apps processes? haha of course not

well, yea, so Ill end up with 2 exact same module definitions per app, which is stupid (edited)

no, the same module in 2 components

There’s this bit in Android Hilt, I would assume some of these are true for classic Dagger

There are three rules to follow when installing a module in multiple components:

• Providers can only be scoped if all of the components support the same scope annotation. For example, a binding provided in 

ViewComponent

 and 

ViewWithFragmentComponent

 can be 

@ViewScoped

 because they both support that scope annotation. A binding provided in 

Fragment

 and 

Service

 can not be scoped with any of the standard scopes. • Providers can only inject bindings if all of the components have access to those bindings. For example, a binding in 

ViewComponent

 and 

ViewWithFragmentComponent

 can inject a 

View

, whereas something bound in 

FragmentComponent

 and 

ServiceComponent

 could not inject either 

Fragment

 or 

Service

. • A child and ancestor component should not install the same module. (Just install the module in the ancestor, and the child will have access to those bindings).

@gildor "no, the same module in 2 components" how so? if the provider method already has @AppScope on it, you cannot attach such module to @UserScope component, canyou? retrofit ok sure, but its incorrect to use @Reusable for some state holder, @Reusable is just a "please cache this for perf reasons, but if not, I dont mind"