WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #36335, comment 52


Ignore:
Timestamp:
06/06/2016 03:51:38 PM (4 years ago)
Author:
schlessera
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36335, comment 52

    v2 v3  
    55However, I would recommend against moving the autoloader manually, this just introduces an unnecessary liability that might cause platform issues. I would just let Composer handle that as well, it includes platform-agnostic filesystem management that is tested on lots of platforms/environments.
    66
     7My recommendation would be to just go with default Composer behavior (less surprises), and have WordPress Core simply assume that classes are present. Moving the autoloader into `wp-includes` gives the impression that this is Core-specific "source" code, while it is in reality only a build-time artifact.
     8
    79EDIT: Ok, noticed the edit in the previous comment too late.
    8 My recommendation would be to just go with default Composer behavior (less surprises), and have WordPress Core simply assume that classes are present. Moving the autoloader into `wp-includes` gives the impression that this is Core-specific "source" code, while it is in reality only a build-time artifact.