A modern programming language that makes developers happier.

kotlinlang

Koin 2.2.0-alpha-1 is out ... Now you can use KOin with Kotlin 1.4 :+1:

is there any docs on it or change log i can't find any

Does this version support multiplatform or is that limited to the 3.0.x artifacts?

<@U2JKKPMEE> how big are the existing API changes in 2.2.0-alpha1 and how `alpha`  it is compared to 2.1.6?

mostly ViewModel API &amp; Scope API changes

checkModules can now check all your modules even with injection params

<@U2JKKPMEE> weird that in 2.2.0 and Kotlin 1.4.0 the last item in `parametersOf()` must be cast to `Any`  and could not be nullable. `Type mismatch: inferred type is String? but Any was expected`
Also could you tell me if I have updated a ViewModel instantiation correctly?
I have replaced the old code
```viewModel = lifecycleScope.getViewModel&lt;FormsViewModel&gt;(this) {
                parametersOf(
                    intent?.getBooleanExtra(ProcessHelper.IntentParamShouldReset, false) ?: false,
                    intent?.getStringExtra("processName")
                )
            }```
to
```val viewModel = scope.getViewModel&lt;FormsViewModel&gt;(null, emptyState(),
                { ViewModelOwner.from(viewModelStore) }, parameters = {
                    parametersOf(
                        intent?.getBooleanExtra(ProcessHelper.IntentParamShouldReset, false)
                            ?: false,
                        intent?.getStringExtra("processName") as Any,
                    )
                }
            )```
Old implementation looks much more cleaner than the current one and also there are many `viewModel(...)` methods, that I found confusing in terms of which I should use. If you could provide some suggestion or samples how it should be used, that will be very much appreciated.
Will describe what I want to achieve  in case you might know the easier way :smile:
```I have an activity that initiates view model and all the fragments and child fragments inside that activity are able to access this view model if needed via Activity. And during activity lifecycle the same instance of ViewModel is delivered to fragments via `getSharedViewModel` call.
In 2.1.6 I done this via activity `lifecycle` 
module definition looks like this:
scope(named&lt;MyActivity&gt;()) {
    viewModel { (intent: Intent?) -&gt; MyViewModel(get(), get(), intent) }
}```

<@USEUPKS0Z> you mean having nullable param injection :thinking_face: ?

Yes, this is needed in order to use same component but with different options. You might have it in one case and might not in the other case. I was thinking, that it should be possible to make multiple definitions with different parameters, but it wasn’t needed previously.