Attila Oláh

> Ok, but is there any way to inject a custom value that is not in the container? You need to register it first.

I wonder if the automatic calling of an initializing function should be introduced to sync version as well. I like the PR but I am not experienced with this project...

> we should change the entire API interface to be fully asynchronous. That has a big performance overhead compared to using the sync API. That would mean serious perf regression...

> I'm not sure that I understand your point, could you elaborate on this please? > ... > If you are not using real async calls to initialize your services...

I am thinking in something like ```ts // pseudo code not real names Container.set({ type: MyAsyncClass, id: MyAsyncClass, async: true }) Container.set({ type: SyncDependingOnAbove, id: SyncDependingOnAbove }) await Container.waitForClassInit() //...

This will be implemented when container inheritance is reworked.

Can you please provide a minimal example of your desired behavior? Including what would you like to happen and what happens currently.

This has a pending PR in #126.

We need to discuss how to surface this API in a useable way. My relevant comment from the PR: > I'm not sure that I understand your point, could you...

> I think there is a very simple solution, but it brings some magic: TypeDI should check if some of the providers return `Promise` - then the whole `container.get()` should...