On 1/20/11 12:15 PM, Bernhard Schussek wrote:
I know I'm repeating myself, but having an explicit inheritance tree
now _and_ encouraging unique bundle names, why don't we include the
full namespace when referring to resources in bundles?
Including the vendor name in the bundle name to make it unique is kinda weird.
Because IMO, including the full class name has three main drawbacks:
* It can make references to resources much longer (of course, it depends
on the number of categories you have in your namespace -- so with only a
vendor and a bundle name, the difference is just 1 character);
* Then, it is more difficult for Symfony to determine what is the class
name and what is the path part (except if you use \ for the class name,
but this looks really ugly then);
* But more important, using the full class name is a strong hint that
you want the resource from this specific bundle, not a child one, which
has obviously a very different name.
Fabien
Bernhard
--
Software Architect& Engineer
Blog: http://webmozarts.com
Twitter: http://twitter.com/webmozart
--
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
