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
Since PSR-0 explicitly mandates that underscores in file names must be translated into directory separators to locate the file the following files will throw an exception:
unless the "composer dumpautoload --optimize" was executed either directly or via the install/update commands (with the "--optimize-autoloader" option).
move the files in subdirectories according to PSR-0, e.g. src/MaxCDN/OAuth/OAuthSignatureMethod_HMAC_SHA1.php shold be moved to src/MaxCDN/OAuth/OAuthSignatureMethod/HMAC/SHA1.php
update the composer to use classmap to include those files
The project's readme currently states that
It is advised that you understand how to optimze Composer's usage in Production environments.
But this could prove to be ill advice as what the --optimize-autoloader option actually does is to scan all included files and dump a classmap for you. This could be an optimization if the project has a sane amount of dependencies/classes, but on legacy projects with tons of seldom used files this has the potential to produce monstrous classmap file (in my case ~600kB :) ) and become anti-optimisation.
The text was updated successfully, but these errors were encountered:
Since PSR-0 explicitly mandates that underscores in file names must be translated into directory separators to locate the file the following files will throw an exception:
unless the "composer dumpautoload --optimize" was executed either directly or via the install/update commands (with the "--optimize-autoloader" option).
There are two possible solutions:
The project's readme currently states that
But this could prove to be ill advice as what the --optimize-autoloader option actually does is to scan all included files and dump a classmap for you. This could be an optimization if the project has a sane amount of dependencies/classes, but on legacy projects with tons of seldom used files this has the potential to produce monstrous classmap file (in my case ~600kB :) ) and become anti-optimisation.
The text was updated successfully, but these errors were encountered: