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

Can you give a example?

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

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

yes I see

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

no I mean, we have

get

to resolve directly

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

sure I see