The second issue is constructor lazy & provide...

# koin-contributors

[Kirill Rozov]

The second issue is constructor lazy & provider injection into constructor. It’s bad to have required dependencies of a component into properties because DI library can’t do that

[Kirill Rozov]

I have written Proxy<T> and Lazy<T> wrappers that resolve dependencies lazy and it will be good to have it build in the library

[arnaud.giuliani]

Can you give a example?

[Kirill Rozov]

class Artifact(
   lazyDep: Lazy<Dep1>
   proxyDep: Proxy<Dep2>
)

module {
    single {
         Artifact(lazyDep = lazy<Dep1>(), proxyDep = proxy<Dep2>())
    }
}

[Kirill Rozov]

It allows injection in a constructor without resolve dependencies immediately

[arnaud.giuliani]

yes I see

[arnaud.giuliani]

can't we use inject() here? 🤔

[Kirill Rozov]

Very important to have static analyzer rule to check confusing between get and lazy, provider

In my own implementation

module {
    single {
         Artifact(lazyDep = get<Dep1>(), proxyDep = get<Dep2>())
    }
}

But will be never successfully resolved

[Kirill Rozov]

can’t we use inject() here? 🤔

Do you mean property injection ?

[arnaud.giuliani]

no I mean, we have get to resolve directly

[arnaud.giuliani]

... I don't have the Koin codebase under the hand 😛

[Kirill Rozov]

no I mean, we have get to resolve directly

But it resolve all dependencies in a constructor when I’ll get Artifact . But I want to resolve them lazy

[arnaud.giuliani]

sure I see