…values Closes #16
…sponse to the README
…ing the result using Injector#getMappedResponse
Additionally, some duplicated code in Injector was moved into helper methods
…y created injectors into child injectors. This is mainly meant to be used in the context of Robotlegs, which subclasses Injector to allow for using swappable injector implementations through a uniform interface. Because SwiftSuspenders must not have a dependency on Robotlegs, we can't internally create an instance of Robotlegs' SwiftSuspendersInjector. Using the public setParentInjector method, it's possible to manually instantiate SwiftSuspendersInjector and set the parent context's injector as the parent injector afterwards.
…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
…ns, numbers with value 0)
…nts to fail Closes #13
…tees, whose dependency resolution wasn't detected early enough.
…t test coverage. Closes #10