The first suggestion I hesitated with a little as I quite liked the
simple top-level structure of app/, src/ and web/, and introducing
vendor/ pollutes that a bit (even if just from a purely aesthetic
POV!).  However I think the meanings of src/ versus new src/ and
vendor/ are equally cohesive, and having a separate top-level
directory called vendor/ for third-party code is a pretty common
pattern (Rails does it).  If of itself I'd be pretty ambivalent about
the change.

I think the second suggestion (adopting /vendor/<Vendor_Name>/
(<Namespace>/)* etc for third-party vendor directory structure in line
with PSR-0) makes perfect sense.

My question is what the best structure would be for the src/
directory.  Should the first directory be a vendor name directory too,
even if that's just a localised 'vendor' called "Application" (or
"App", for consistency) by default?

So:

/src
  /App
    /Bundle

Or is there still a need for a top(pish)-level non-third-party
directory for bundles?

So
/src
  /apps
    /(<Application_Name>)+
  /bundles
    /<Own_Vendor_Name>
      /<Bundle_Namespace>
etc?

Douglas

-- 
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

Reply via email to