fabpot/Silex — Issue #249: communicate best practice for third party extensions
Author: ivoba
Created: 2012-02-07 08:41:38+00:00
State: open

It would be good, i guess, to have a common stucture for third party extensions, that should cover the location of the extensions in the vendor dir and also for dependency handling.

During my work with Silex i came across extensions which communicated a placement in vendor/Extension, vendor/Silex-Extensions, vendor/SilexExtensions andsomemore.
Then they where dependency handling with vendor.sh, .gitmodules or composer.
Also there are some Collections of Extensions on github, which i would say are also not optimal to include in your project.

Silex is great and i believe the number and usage of third party extensions will increase, so maybe it would be good to have some "official" words on that.