WordPress.org

Make WordPress Core

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


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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36335, comment 52

    v1 v2  
    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
     7EDIT: Ok, noticed the edit in the previous comment too late.
    78My 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.