@Fabien: > Here is my implementation, with all the answers to your questions in the > commit message:
Discussed it over lunch with Lukas, maybe it should throw an exception if two bundles define the same parent, to avoid any strange errors to happen by mistake. On Thu, Jan 20, 2011 at 12:15 PM, Bernhard Schussek <[email protected]> wrote: > I know I'm repeating myself, but having an explicit inheritance tree > now _and_ encouraging unique bundle names, why don't we include the > full namespace when referring to resources in bundles? > > Including the vendor name in the bundle name to make it unique is kinda weird. I agree in principle, but imagine the template includes and stuff if you'd have the full namespace: {% extends "Vendor\Bundle\BlogBundle:Foo:index.php.html" %} vs . {% extends "VendorBlogBundle:Foo:index.php.html" %} Of course if the class name were: Vendor\Bundle\Blog\BlogBundle then it'd become: {% extends "Vendor\Bundle\Blog:Foo:index.php.html" %} Which is more acceptable, actually only two chars more. Fabien: I still fail to see the reason why you want the bundle namespace to be called BlogBundle, it's already in the Bundle category, and the class name also identifies it as a bundle. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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
