Larry already mentioned `auto_append_file` that I also think is the way to go, if it fits.
The example directory structure from your email is also considered insecure, because without proper web-server protection, you are essentially exposing _all_ `vendor` files, including the ones that potentially execute code. On Sat, Mar 27, 2021 at 10:23 PM Abdul Haq Sheikh <khaweronl...@gmail.com> wrote: > > If we want to use composer packages, we have to include > 'vendor/autoload.php', and if we don't have a front controller design > pattern, we must include 'vendor/autoload.php' on every/most files. Why not > to auto include 'vendor/autoload.php' file (if vendor folder exists)? > * PHP will use include_once to include file > > Example Directory Structure: > - Index.php (file) > - Test.php (file) > - Classes (folder) > -- Classes/test2.php (file) > - Vendor (folder) > > - On Index.php, php will automatically include 'vendor/autoload.php' > because the vendor directory exists. > - On Test.php, php will automatically include 'vendor/autoload.php' > because the vendor directory exists. > - On Classes/test2.php, since file is in sub directory and here vendor > directory doesn't exist, so php will not include 'vendor/autoload.php' -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php