Hi. First of all thanks for Koin. great tool. Have a question: I’ve been busy with migrating to 2.0 - everything is good, but how do I mock/override definitions in scopes? (for testing) Thanks

Hello everyone, I am using Koin to inject shared preferences instance. I have one instance which works fine, but now i would like to add the second. How can I distinguish which one should be used? Here is my implementation:

val preferencesModule = module {
    single { provideSettingsPreferences(androidApplication()) }
}

private const val PREFERENCES_FILE_KEY = "com.myapp.shared_preferences"

private fun provideSettingsPreferences(app: Application): SharedPreferences =
        app.getSharedPreferences(PREFERENCES_FILE_KEY, Context.MODE_PRIVATE)

I think I'll go with zero arg constructor and

by inject

at the top of the class, looks nicer anyway

I’m wondering which is the best way for handle a multi-module app with koin. Actually I got an Android project and a structure like this (

->

= depends by ):

app -> feature modules 
&
app -> "DImodules" module
&
DImodules -> all other modules ( feature and business )

In this way app takes a reference to all the koin modules from DImodules, without directly depend by them, but I don’t think this is an awesome solution. Also I would like to invert the dependencies and let feature modules depends by app, but in this way I would have a dependency circle

features -> app -> DImodules -> features

. Removing DImodules I wouldn’t know how to initialize other modules 🙄

Koin 2.0 is out: https://medium.com/koin-developers/ready-for-koin-2-0-2722ab59cac3

in koin 2.0 how can we use

org.koin.android.ext.android.setProperty

??

Hello, I just started using koin in ktor project and I added additional functionality to allow registration of singleton by KClass argument e.g.:

// Register by KClass
private fun Module.single(
    type: KClass<*>,
    createdAtStart: Boolean = false,
    override: Boolean = false
): BeanDefinition<*> {
    val beanDefinition = BeanDefinition<Any>(
        qualifier = null,
        scopeName = null,
        primaryType = type
    ).apply {
        this.definition = {
            val constructor = type.getFirstJavaConstructor()
            val args = getArguments(constructor, this)

            constructor.makeInstance(args)
        }
        this.kind = Kind.Single
    }

    declareDefinition(beanDefinition, Options(createdAtStart, override))

    return beanDefinition
}

// Inject by KClass
private fun <T : Any> Application.inject(type: KClass<T>): Lazy<T> = lazy { getKoin().rootScope.get(type.java) }

// Module declaration
val myModule = module {
    // findKClasses - returns List<KClass<*>>
    findKClasses().forEach { single(it) }
}

We have classes that we need to resolve dynamically by KClass so that is why we need an ability to register them by KClass. It works now but I wonder how much this code is prone to breaking changes in the future. Or is there an "official way" to achieve this?

guys, I have some doubts about how longer lives a single instance and the result of a factory instances. I already understand that single=bean=a lazy instance that can be reused anytime that it’s needed, and factory is a factory of these beans = singles. My main doubt is, if I have a factory of usecases/interactors, how long will live usecase1, usecase2 etc? Is this always engaged with application scope? Or should I define a new scope to make my usecase lives until viewmodel.onCleared(e.g)?

In the past, we could use a string name.... This doesn't seem to work any more because the lookups in the last life cycle scope seems to use the activity name always...

What is the best practice in handling koin modules in multimodule project? I ‘ve come up with solution that each module will provide list od modules that he wants to load to the whole graph and in the top level App module I will gather all of these and put them inside loadKoinModules function but maybe there is something better?

is your gradle config file ok?

in

getViewModel

you can pass a KClass & the name is considered as the key

Hi! I have a bunch of fragments, each with their own viewmodel, that will act as a ‘wizard’/‘workflow’ with multiple states. I have used the Tinder StateMachine library for state implementation. Could someone please point me in the right direction for state sharing between fragments/viewmodels? I figure I have to write a KOIN shared viewmodel, but I am not sure I have understood the full picture and need a tip… Thanks!

Is it possible to have multibinding with Koin as intoMap or intoSet functionalities like in Dagger2?

Hey folks, after getting the latest update of android studio I’m getting a suggestion to remove the casting of interfaces in koin module. However if I remove that casting it crashes the application. is there a way to tell android studio that this suggestion is not valid?

here how it looks

Hi! I was wondering if there was a performance gap between

single { ClassA() }  
 // ClassA's using by inject

And

single { ClassA(get()) }

In case I do not use the global Koin instance but go with koinApplication (which by naming I assume answer will be no) - is there a way to extend the instance and create a new one?

Hi @arnaud.giuliani, I don't see any new API update for Room. I need your inputs to test basic CRUD operation using koin-test with latest Koin-2.0.1. Attached my code. I got null pointer exception while executed.

Why is android studio not resolving

by sharedViewModel()

? I have all the dependencies...

hi there, I have a lot of repitions in my koin log. I wonder if this is normal or pointing to some kind of circular dependency.

I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'android.content.Context'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'android.content.Context'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
I/KOIN: +-- 'my.app.components.application.LocalizationHelper'
I/KOIN: +-- 'my.app.components.data.DataFormatter'
...

the actual output is around three times longer.

I'm trying to understand scopes in Koin 2.0.1, and why they have both a name and an ID. The only purpose I can see would be two have multiple instances of a given named scope active at the same time. Which works, but then if you close any one of those scope, the others with the same name (but different ID) are no longer usable. What's the point?

Morning! How do you access to Koin Context from an extension? Looks a lil' bit weird do somwthing like

KoinJavaComponent.get()

and too verbose to do a

StandAloneContext.getKoin().koinContext.get()

, there are other options?

Regarding MP, there is this PR going on: https://github.com/InsertKoinIO/koin/pull/519

wondering if anyone has looked into configuring static analysis for koin - e.g. to warn you if you're injecting a class that isn't in your modules

Just had a weird behaviour on lint. I have this module, but for some reason the cast as CarsRepository is declared not needed. But it’s actually mandatory otherwise at runtime the application crashes 😮

val remoteModule = module {
    factory { CarRemoteRepositoryImpl() as CarsRepository }
}

How can I debug this from Koin core side?

hello people, What is the androidLogger() used for in the startKoin function?

how do I inject the databaseDAO directly with koin? It says it doesn't have enough information to infer type variable T... Why does it need to be a

val

?

I'm adding koin to my library, wish me luck