Conversation
…(i.e. for unit testing a controller).
|
injectAll sounds weird...what about injectOn? |
|
I used injectAll because that feature existed in previous versions (< v3). It's short for "inject all dependencies", whereas "inject" is more "inject x into y" and the method takes only one param, so that's confusing. I'm ok for injectOn. That would even leave the possibility later to add another parameter to specify which dependency to inject. That can be useful for example in the tests, if you are creating an object with mock dependencies, but there is one dependency of that object that you don't want to mock. |
|
I could see that being useful: |
…ents & aliases prior to local namespace to match how php5 resolver works.
For #87 changed the annotation type parser to resolve with use statement...
|
Release 3.3.0 published: https://github.com/mnapoli/PHP-DI/releases/tag/3.3.0 |
Container::injectOn()PhpDocParserinjectAllintoinjectOninjectOn