Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #36335, comment 261


Ignore:
Timestamp:
11/07/2022 02:22:31 AM (19 months ago)
Author:
omaeyusuke
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36335, comment 261

    v1 v2  
    11Replying to [comment:259 jqz]:
    22> I don't understand this concern.  AFAIK, Composer doesn't generate any superfluous files.
    3 No, there are files that are required considering the resolution of dependencies on packages created by third parties, but unnecessary considering only the autoloader into the core (e.g., autoload_psr4.php, autoload_real.php, ClassLoader.php) .
     3No, there are files that are required considering the resolution of dependencies on packages created by third parties, but unnecessary considering only the autoloader into the core (e.g., autoload_psr4.php, autoload_real.php, autoload_namespace.php) .
    44If you do not do dependency resolution for third-party created packages, most of them could simply be overhead if we use Composer as a whole.
    55> Isn't the point of this to reduce the number of files, as well as eliminating version conflicts when two plugins ship with incompatible versions of a third-party package, by sharing common packages between plugins/themes, and having WordPress download and install the dependencies to a common folder (e.g. wp-content/packages) rather than the plugins/themes having to ship with separate copies of these common packages.