Is it possible to iterate over all declared dependencies from an specific module?

In terms of scoping with Koin, after starting Koin in application.onCreate, does it make sense in trying to achieve scoped dependencies by loading(onCreate)/unloading(onDestroy) new modules on the fly in Activities/Fragments. For example, in Activity A, I would load/unload modules (A1,A2) and in FragmentB and FragmentC (that would be presented in Activity A) I would load/unload modules (B1,B2 for FragmentB) as well as (C1,C2 for FragmentC). My understanding is that all definitions in A1/A2 would be available and shared between A,B and C(meaning a single { } would be the same between A,B,C). Is that correct?

Hello, how do I use different injections for tests? Similar to spring profiles. I'm trying to start a test with a different set of components than my main app. (Local db, etc) I've tried the override=true flag, but it's not doing anything. My production components are always called

I tried adding

createdAtStart = true

to the

single

declaration but it still does not get created at startup.

For Android, Dagger is now recommended by Google... https://developer.android.com/training/dependency-injection#choosing-right-di-tool

I think the rationale would be that larger apps have a larger number of dependencies that will be injected throughout. A service locator, or a runtime DI library, would necessarily need to know about each and every dependency available throughout the lifetime of the app in some ever-growing singleton object. In contrast, Dagger generates code and doesn’t really “hold on” to anything; it simply executes generated code whenever injection is requested, but it doesn’t need to hold in memory some kind of “binding object” in order to be able to inject stuff

Question: When creating a module definition Koin complaints when having more than 5 parameters. Is this a limitation in the current version? If so; Why?

Can someone please explain why everyone says that koin is a service locator and Dagger is a 'true' DI? I don't see any semantic differences in module definitions and what I understand from service locators is completely different from koin(sth like androids

context.getSystemService

)

If you’re looking to make a new docs site, I would encourage you to check out Orchid. I’ve been creating it specifically for docs like Koin, and I would be more than happy to work with you to get it set up. Orchid can do your wikis, integrates with Dokka, and much more https://github.com/javaeden/orchid

can Koin inject some named parameters in a constructor like this

class Testclass @Inject constructor(
    @Named("some_name") name: String)

?

Also, how can I use koin before starting the ktor server in my test?

Incoming new stuffs guys 🎉

Question, I have multiple modules, both pure-kotlin and Android. My idea was to have all the modules load a service-provider wich provides a Koin-module. Therefor, I only need to create the Modules. I want to do as much as possible in Kotlin-only modules. The simplest way to do this is by using kotlin-core everywhere with the exception of the base-app where I use those modules... Is this correct and is this possible?

Is there a notion a

Reusable

the same way Dagger has ? I can’t find it, would anyone be interested ? many times I don’t really need singletons but I don’t need to create a new instance either

is it possible to merge modules without starting a koin?

And seem to be having an issue creating an instance

org.koin.core.error.InstanceCreationException: Could not create instance for [type:Factory,primary_type:'com.gaurav.koin2.PaymentViewModel']

#koin any idea what could be wrong ?

@g4sarma What does your

PaymentViewModel

look like? My guess is it has a dependency that Koin doesn’t about. So that’s why Koin cannot create it.

PaymentViewModel(*Koin doesnt know about this dependency*))

What’s the difference between retrieving an instance of a viewmodel by using

getViewModel

and

get

?

Is it intentional that fragment accepts Qualifier? https://github.com/InsertKoinIO/koin/blob/develop/koin-projects/koin-androidx-fragment/src/main/java/org/koin/androidx/fragment/dsl/ModuleExt.kt

hi all, This is a general question. How is Koin not generating code? I need to learn more about how it works. Compared to dagger which does generate code.

Following your post lead to Martin Fowler. If I get this right, it means that Koin have a built in parser that can understand Koin DSL, at run time, and just execute it like Kotlin code. Am I right?

In other words, is Koin “single” definition threadsafe?

In this case KoinRepositoryLetters depends on KoinRepoA(), KoinRepoB(), KoinRepoC(), which all take a ServiceA, ServiceB and ServiceC The error I get is that the bean definition for KoinRepoA() is not found

What's the difference between single and singleby here https://github.com/InsertKoinIO/getting-started-koin-ktor/blob/master/src/main/kotlin/org/koin/sample/HelloAppModule.kt#L8

Just wanted to point out that https://start.insert-koin.io/#/getting-started/modules-definitions is down

Hi Koin community, First of all thanks for the amazing Koin solution and apologies for posting basic (if not stupid 😃) questions here. I am considering using Koin in production app and before doing that I would love to get a clarity on the below to see a bigger picture in moving confidently for the migration. Our prod code base is huge. We are using dagger for DI and it also has multiple modules. 1. Migrating to Koin in our project has to be done in step by step process so can I use koin and dagger parallelly in same project ? 2. If yes how do I use koin module inside a dagger component and dagger module inside a Koin component during the period of migration ? 3. Is it safe to use Koin in big scale and multi module project or is there any pitfalls that I should be aware of based on your experiences ? Thanks in advance and any help or advice would be appreciated.

try to detach about Dagger and its complexity as much as possible

Good way to demonstrate to team as a POC 👍