Hi,
Isolating the vendor directory to the root makes sense to me because the
libraries have nothing to do with the application code.
This is a very common practice.
Regarding the bundles, the current structure, with Bundle under src/ makes a
lot of sense to me since these bundles should always be part of the
application. The others are part of third-party libraries.
It makes also sense to have the namespace starting with "Bundle".
"Symfony\Bundle\" has its place into vendor directory.
This makes even more sense if we assimilate the src/Bundle directory to a
"modules" one, in a CMS context for example.
(modules = Bundle)
src/
app/
modules/
Backend
Frontend
News
vendor/
Anonymation/
Component/
That makes more sense than :
src/
app/
Anonymation/
Module/
Backend
News
No ?
And, as it was said, having a namespace like "Anonymation/Bundle/NewsBundle"
makes difficult (not difficult but ugly :p) to override bundles resources,
like views.
Now for the "Application" directory, maybe its name is not appropriate since
it is seen as a "shared" part of the application code. Maybe it should be
renamed for more clarity.
--
Benjamin Dulau - anonymation CEO/DSI
anonymation.com | code.anonymation.com
[email protected]
--
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
