You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the same order as given in the JSON, to give users control about the autoloading order.
While the single tools put their own autoloader on top ("vendor-bin/tools/dev/autoload.php"):
Note: Including each another file does not lead to endless recursive includes.
The require_once returns the object on the first include and just TRUE for any further call.
The text was updated successfully, but these errors were encountered:
I think combining the autoloaders of multiple vendor-bin is a terrible idea: it completely defeat the purpose of Composer which is to prevent you to autoload incompatible code and will lead to subtle and terribly hard to debug issues that can pop up at any time.
Right now every package namespace creates its own autoloader:
From my own experience and lately discussed in composer/composer#9636
a custom autoloader could be a thing:
Right now developer can do this on their own:
But this needs some hands on when adding another section
Having this more dynamically would be a little helper.
Suggestion
The common/central "vendor/autoload.php" should be changed to:
In the same order as given in the JSON, to give users control about the autoloading order.
While the single tools put their own autoloader on top ("vendor-bin/tools/dev/autoload.php"):
Something like this (just a quick fuzzy example).
Note: Including each another file does not lead to endless recursive includes.
The
require_once
returns the object on the first include and justTRUE
for any further call.The text was updated successfully, but these errors were encountered: