Can you explain why you would want to disable interface injection for an
entire service?

The use cases I see are that you want to disable injection for an entire
interface, e.g. for ContainerAwareInterface, or that you want to disable
injection for an interface for a specific service (e.g. generally you want
injection through the interface to happen, but for one specific service you
want to inject a different dependency).

I just can't make something up for disabling injection for all interfaces
that a service has implemented.

My vote still goes for solution 6). Also keep in mind that if we add another
flag, then we also need to think about how that is inherited, e.g. if
another definition inherits from a definition which has interface injection
turned off, is it now also turned off for the entire child service? This
would be a big limitation.

Johannes

On Sun, Apr 17, 2011 at 2:54 PM, Lukas Kahwe Smith <[email protected]>wrote:

>
> 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
>

-- 
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

Reply via email to