Hello, The past few days I have been looking into Symfony2 and I had some concerns regarding the lack of flexibility in naming Controllers and possible naming collisions for Bundles.
While every single class in Sf2 is namespaced, it struck me that controller names in routes and template names are not fully qualified and ambiguous when you have more than one Bundle with the same name. While I understand your best practices for naming Bundles try to work around that, I do feel it's counter-intuitive (as the Bundle is already properly namespaced), and I do not understand why not specify a fully qualified controller name to start with, as it's only slightly more verbose and avoids any ambiguity. Another related concern is about the flexibility of naming controllers, as currently a pattern of NameSpace\BundleName\Controller \FooController is hard-coded in ControllerResolver.php, leaving little flexibility to that regard. Again, using fully qualified names for the controllers would avoid this issue. The problem also extends to view names, though I haven't had the chance looking further into that part. Regards, Gerry. -- 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
