On 14.04.2011, at 17:03, Bulat Shakirzyanov wrote: > I will also not work for not previously frozen container, as the > applyInterfaceInjectors method call is called last. > Any "per-method" injection disabling won't work in that case > I'm +1 on disabling II for the whole definition as we can then achieve > consistent results for both container types
I know that for many this topic isnt so urgent. For me it is though, so I would appreciate it if we can wrap this up. My vote is the same as Bulat, aka being able to disable interface injection on a per service basis. As soon as we have a clear decision I will implement it. Thanks. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
