Hello. I need some explanation on "how to do hierarchy" in koin e.g. I need differently created retr...

# koin

[Va Fu]

Hello. I need some explanation on "how to do hierarchy" in koin
e.g. I need differently created retrofit instances for different activities. I can do it by calling startKoin with all modules needed at each activity, that's seems to be ok
but I have, for example, a DB manager, that must be application-scoped. by calling startKoin each time i need to provide new instance of DBModule and that's seems not to be OK, 'cause of new instances are about to create in new context.

using dagger I could have activity component is somehow related to the main component. how could I achieve the same using koin?

btw, still I love this library so far, ty ❤️

[arnaud.giuliani]

Hi @Va Fu `startKoin`must be called just once - in your Application class.

[arnaud.giuliani]

if you provide components directly, it will be in application scope

[arnaud.giuliani]

you can open `context`secvtions to describe sub contexts that you can drop

[Va Fu]

ok, to the test project 😄

[arnaud.giuliani]

check the sample project if you want

[Va Fu]

here I have a simple wrapper that provides Conductor's router instance for each activity

[Va Fu]

holly molly, I cannot post photos to thread, sorry