On Thu, Jan 20, 2011 at 2:05 PM, stof <[email protected]> wrote: > But it is your choice to put "Bundle" before the bundle name in the > namespace or not. If you don't need to have bundles and components in your > namespace you can drop it (you can also drop it anyway and rely on the next > part of the namespace to recognize bundles as they are *Bundle). > the Symfony namespace defines lots of components so it seems logical to > separate them from the bundle but this is probably not the case for most of > the vendor namespaces.
You're not getting my point.. I know I can do what I want in my app, but the fact is that in the Symfony namespace, Components don't have the FooComponent name, so I would like to hear a good reason why Bundles should be called FooBundle. And recognition is not valid imo since it's in the namespace and in the class name already. 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
