Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
interfaceInjectionEnabled="false" in the service disables interface injection#547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…efinition disables interface injection
kriswallsmith commentedApr 13, 2011
Looks good to me. I would just change the semantics to |
lsmith77 commentedApr 13, 2011
yeah .. would be more consistent with abstract and synthetic |
lsmith77 commentedApr 13, 2011
it seems PHPDumper also needs to be fixed. the point is that right now interface injection prevents granular dependency management, which imho is unacceptable. worse yet this breaks my solution for fixing the same issue with people injecting the container (aka ContainerWrapperBundle). i think we are perverting DI and the DIC concept and i want some way to regain control. sorry for the rant. |
avalanche123 commentedApr 13, 2011
I am 👍 on the change as long as PHPDumper gets updated too. I don't think it is useful to be able to disable interface injection, but I don't see how else you could avoid automatic injection. I'll read up on how other container get around this and post my thoughts here |
lsmith77 commentedApr 21, 2011
closing since we will remove interface injection |
interfaceInjectionEnabled="false" (defaults to true) in the service definition disables interface injection
see#544 for more discussion on that topic and yet more links to other discussions :)