Hey Gerry I agree the standard feels strange (since you repeat the namespace in the bundle name). And while the current implementation doesn't really bother me, I can't really think of an answer to your question.
Does anyone know what's wrong with using the namespace as the bundle name. I suppose that would mean SensioHelloBundle would become Sensio\HelloBundle (and the bundle class could be called anything)? @weaverryan On Feb 24, 2011 4:43 AM, "Gerry" <[email protected]> wrote: >> Many bundles were created before these best practices were written. >> >> Thus one issue when searching a bundle now is being sure it has been >> updated to follow the changes of the framework. Some of them are totally >> outdated > > But that doesn't really speak for not using FQN's either. While we can > minimize the potential problematic situations, is there a reason for > not changing it? > > -- > 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 -- 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
