Hi! Why can't Koin search for classes registered for DI that implement an interface that is required by some other component?

Hello! I'm wondering if anyone could elaborate on the differences between the AndroidX package 

org.koin:koin-androidx-viewmodel:$koin_version

 versus just the basic 

org.koin:koin-android-viewmodel:$koin_version

. I have been using the latter with ViewModels from the AndroidX lifecycle package and everything is working just fine. What would I need the AndroidX Koin dependency for?

will help merge and better manage all docs

I'm getting this error when I try to build my KMM project

Incompatible Kotlin/Native libraries
				There are 2 third-party libraries attached to the project that were compiled with an older Kotlin/Native compiler and cant be read in IDE:
				Gradle: org.koin:koin-core-metadata:darwinMain:3.0.0-alpha-4
				Gradle: org.koin:koin-core-metadata:nativeMain:3.0.0-alpha-4
				Please edit Gradle buildfile(s) and specify library a version compatible with Kotlin/Native 1.4.30-RC. Then re-import the project in IDE.

I'm using AS 4.1.2 and the Kotlin version

1.4.30-RC

, any way I can fix this?

I noticed the docs still mention jcenter(). Is there an alternative repository to use? https://insert-koin.io/docs/quickstart/kotlin/ EDIT: I just noticed https://github.com/InsertKoinIO/koin/issues/1004

hi, posting this issue cause I think everyone trying to update to compose alpha12 will have it: https://github.com/InsertKoinIO/koin/issues/1006

Is there any way to construct

NavArgs

on the fly and inject then directly into

ViewModel

?

Sharing it here as it’s relevant for people in this channel 🙂 https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1613409760212800

Hello Is there a way to get androidContext() mocked in my module for a unit test ?

new article: https://proandroiddev.com/understanding-android-scopes-with-koin-cfe6b60ca579

Hey folks, is it a bad practice to get the Fragment's Presenter (MVP arch) lazily via

by inject

like this:

private val presenter: MySamplePresenter by inject { parametersOf(requireContext(), get()) }

at the top of the Fragment? (not in lifecycle events like onViewCreated etc). Is this gonna cause a memory leak on screen rotation? (cause then fragment is retained during configuration change but view is destroyed and recreated)

hello guys. I’m trying to add koin gradle plugin

classpath "org.koin:koin-gradle-plugin:3.0.0-alpha4"

, but getting error

is it being removed from koin? How can I check dependencies now

How can a dependency be scoped to a sharedViewModel and then be injected into a non-shared viewModel?

Hey there, I’m attempting to migrate from 

org.koin:koin-core:3.0.0-alpha-4

 to 

io.insert-koin:koin-core:3.0.1-beta-1

  but I can no longer import 

org.koin.core.get

,

org.koin.core.KoinComponent

or

org.koin.core.inject

, has anyone else seen this issue/know how to resolve it?

I'm trying to also migrate to the 3.0.1 beta version but I'm getting errors. Any idea why this is?

Failed to resolve: org.koin:koin-core:3.0.1-beta-1
Failed to resolve: org.koin:koin-test:3.0.1-beta-1
Failed to resolve: org.koin:koin-android:3.0.1-beta-1
Failed to resolve: org.koin:koin-androidx-viewmodel:3.0.1-beta-1

Hello all, just a reminder on Koin v3 setup: https://insert-koin.io/docs/setup/v3

I can understand it very well that it can be out of the scope of the project, but maybe it's an idea to load properties from a properties-file from commonMain using the gradle-plugin?

How should Compose elements that have injection work with

@Preview

annotation? For me it gives

java.lang.IllegalStateException: KoinApplication has not been started

because application isn’t started during

compose preview

🤔

does maven central repo with version 3.0.1-beta-2 is only for multiplatform? or can be used in android too? I have used new group id (

io.insert-koin

) and it gives error in android studio for viewmodel

I’m trying to run my test suite which uses koin multithreaded and it does not work as expected. I just want multiple koin instances to be independent from each other. this test illustrates the problem:

@Test
    fun `multi instance koin`() {
        class User()

        val user = User()

        val myModule = module {
            single {user}
        }
        fun app()  = koinApplication { modules(myModule) }
        val koin1 = app()
        val koin2 = app()

        koin1.koin.get<User>()
        koin1.close()
        koin2.koin.get<User>()


    }

Hi, I have just noticed that koin strips quotes out of environment variables.

fun saveProperties(properties: Properties) {
        if (_koin.logger.isAt(Level.DEBUG)) {
            _koin.logger.debug("load ${properties.size} properties")
        }

        val propertiesMapValues = properties.toMap() as Map<String, String>
        propertiesMapValues.forEach { (k: String, v: String) ->
            saveProperty(k, v.quoted())
        }
    }

v.quoted()

is the culprit This makes it very hard to put JSON in environment variables and get it back such that parsers don’t complain! Why are quotes being stripped?

Can I inject nullable

DefinitionParameters

to android

ViewModel

in koin? It fails when I try to and value is

null

(

InstanceCreationException

is thrown).

so

jcenter()

should be removed soon, doing so right now breaks the imports

Weird that with

3.0.1-beta-2

the

io.insert-koin:koin-androidx-compose

isn’t discoverable. While with beta 1 it works just fine. Am I missed some changes to packages?

Is there a right way to use Jetpack Compose Navigation components with Koin?

Just wondering, why wouldn't Koin have a logging wrapper like KotlinLogging does, with lambdas to provide the text only if that logging level is enabled? It would add much more value to the wrapper...

Any short way to inject a child of:

interface UseCase<in Request : Any> {
    suspend fun execute(request: Request): ServerResponse

    suspend operator fun invoke(request: Request): ServerResponse = execute(request)
}

in a ktor

fun Route.someRoutes()

using the `Request`'s type? I want to be able to provide an implementation in Unit tests without mocking the actual implementation for that route... and the

Request

object is unique for each

UseCase

...