…nts to fail Closes #13
…e entire injectionConfig.
…ion mappings for parts of a dependency tree In addition, injection results classes have been refactored to inherit from a base class instead of implementing an interface to facilitate code-reuse
…et assigned a fixed InjectionConfig which may or may not already have a result to return instead of querying the Injectors mappings each time an injection request for the InjectionPoint is made. Reasoning for this change: The InjectionConfig shouldn't be resolved anew each time a request for its result is made. Also, this is the last big step of preparation for creating child injectors that forward requests they can't fulfill themself to a parent injector.
…in the InjectionConfig instead of being transferred through InjectionPoint
…eir injector reference at creation time instead of through the InjectionPoint
…tees, whose dependency resolution wasn't detected early enough.
…t test coverage. Closes #10
…tions Tests for the new functionality have been added as well. Closes #5
…red with tests.
…ookup happens as late as possible.
…n with the relevant unit tests
…t header referencing that file
…ctionConfig, added license headers to all IInjectionResult classes, slight formatting changes