I like the way the current system works: - Resources are part of the Bundle world, so having to write Bundle in the Resource path duplicate information. - Namespaces are part of the PHP world. having the Bundle keyword creates a clear boundary between the Component, Lib and Bundle.
my 2c. On 30 mars 2011, at 15:13, Fabien Potencier wrote: > On 3/30/11 3:07 PM, Christian Schaefer wrote: >> I feel I kind of started this so I might as well add my two cents to it. >> >> imho the suffix is there to distinguish between bundles and other code >> like components, bridges or libraries and rightly so as bundles have a >> special meaning in Symfony2. >> >> to be able to use this suffix or not to forces users to make a choice - >> conciously or not which wasn't necesary before as there was only one way. >> >> so if there now is an alternative way then what is the benefit I ask? >> saving a few bytes? that can not seriously be the reason. >> >> imho the suffix should either be enforced or removed altogether >> including folder names to not violate PSR-0. where the second option >> clearly violates my first point of being able to distinguish bundles >> from other code. >> >> leaving the choice to the developer will eventually lead to different >> developers taking different decisions which will eventually lead to >> inconsistencies throughout projects when 3rd party bundles are used that >> follow different naming schemes. > > To clear things up: > > The *only* change was the removal of the Bundle suffix when referencing a > bundle name, that's all. > > *Everything* else is exactly the same as before. The developer has no choice > about the naming of its bundles (not more and not less than before). > > Fabien > >> and again: for what benefit? I just don't get it. >> >> >> +1 for adding it back >> >> -- >> 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 -- 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
