Make containers named and instantiable about typedi

[pleerock]

Api looks good. Btw is there a reason to call Container.create? I think no, because its extra operation which do not do anything - named container can be created when you put @Service with custom container name.

[slavafomin]

@pleerock Yes, I was thinking the same. I've replaced create() with get() above. Is it ok?

[pleerock]

We were talking about separate containers to prevent "clear" method creation in tests, but we anyway endup doing that 🤣

All what we did - we created "named containers". I believe this feature will be rarely used.

I think instead of Container.get("container-name").get(Service) we just do Container.get(service: string|Function, containerName: string = "default")

[pleerock]

do you have in plans to work on this issue? - so we can release everything together in next 0.5.0 version.

[slavafomin]

@pleerock I think we should leave it for now. I'm personally not requiring this functionality at the moment. Lets see if someone needs it. @ALL please feel free to vote on the first post in this thread.

[pleerock]

This feature request was implemented and will be released in 0.6.0. Example of usage:

const controller1 = Container.of("mycontainer1").get(QuestionController);
controller1.save("Timber");
Container.reset("mycontainer1");

const controller2 = Container.of("mycontainer2").get(QuestionController);
controller2.save("Slava"); // different controller instance
Container.reset("mycontainer2");

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.