On Thu, Jan 20, 2011 at 1:26 PM, Bernhard Schussek <[email protected]> wrote: >> 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. > > We had this discussion before. The decision AFAIR was to make class > and namespace names as short as possible, but not short enough for > them to lose their meaning. (e.g., "Blog" is too short, "BlogBundle" > is sufficiently descriptive, "VendorBlogBundle" is overkill IMO).
But there is already Bundle right before Blog in the namespace, and the class name contains both, so it seems quite meaningful to me. Nobody is ever going to look at just "Blog" and wonder what it is. Of course we can do what we want in our application code, but I'd like the Symfony namespace to follow/demonstrate best practices, and Symfony\(Bundle|Component)\$Name sounds good to me, you don't need NameComponent to know what it is, so why do you need that for bundles? 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
