@vicb please update the doc too

@stof good catch thanks, I'll update tomorrow.

@stof @lsmith77 @fabpot what about having PrependExtensionInterface extends ExtensionInterface to avoid having to implements ExtensionInterface, PrependExtensionInterface ?

That looks wrong to me and that's not what we've done with other specialized interfaces that we added in the past for other components.

you are right

I think the question simply is whether there is a reason to implement
PrependExtensionInterface without ExtensionInterface. If you always have to
implement the latter when using the former, then you can as well extend it
directly, no?

On Thu, Jan 24, 2013 at 9:03 AM, Victor Berchet notifications@github.comwrote:

you are right

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/6853#issuecomment-12641197.

I agree.

@lsmith77 @fabpot @stof One more question: does prepend really solve anything ? What if multiple bundles prepend ? A solution could be to have some kind of priorities, what do you think ?

@schmittjoh sometimes you have MyExt extends Extension implements PrependExtensionInterface having PrependExtensionInterface extends ExtensionInterface would look messy.

@vicb we discussed this in the PR .. the assumption is that there will be very few prepending extensions. more importantly these will be mostly applications. in the original implementation it was required for the user to explicitly enable the behavior which would make it possible to prevent conflicts.

I also find the name unfortunate as we do not prepend an extension but some settings