hmlongco
Ability to resolve multiple implementations of same type
This PR adds the ability to resolve all registered implementations for a given type, where the implementations are differentiated by names. Please let me know what I can optimize.
So the first question is why? I'm not sure of the use case or what problem this will solve.
Secondarily, if you're nesting containers for mocking or modularization, then the current code only gets the first set of items it finds. It doesn't get "all" of them.
Valid question!
To your first one: being able to resolve multiple instances of the same registered type is something I am used to when working with .Net. Microsofts Dependency Injection framework and Autofac provide options for that. In my specific case I have multiple classes acting as handlers for some task and all of them need to perform their task. Makes it simple using DI for it so I can easily add new handlers.
Good catch on the nested containers, will look into that.
@hmlongco I addressed your feedback about the nested containers. Can you please review?
Went through this again and found that it still suffers from a bug when handling multiple containers.
Functionally this mechanism gathers up all of the named containers and stuffs them into an array so you can call them as needed. Right?
So what happens if container B is a child of container A... and container A has a named registration of "Fred" that was supposed to override the Fred in container B? In the current implementation both Freds will be gathered, returned and executed... and I don't think that's the desired result.
Terribly sorry for the delay. Been working on getting Factory, my latest DI system, out the door.
I'll put this in if you still want it, but one more change is needed; Throwing a fatal error if nothing is found doesn't make sense. Just return an empty array.
Addressed your PR review comments @hmlongco
Sorry for my delay this time (was on PTO).
