Skip to content

Can this be simplified to one autoloader? #5

@salcode

Description

@salcode

First, let me just say this is a cool project. I always enjoy your perspective on OOP, in particular in relation to WordPress.

In regards to this issue specifically, in basic-scaffold.php we attempt to use the Composer auto-loader and fall back to a bundled auto-loader if Composer is not present.

Having two autoloaders seems like extra complexity.

If we're going to have the Infrastructure\Autoloader anyway, perhaps we could use that (and remove Composer autoloading support).

Alternatively, Composer usage could be required and the Infrastructure\Autoloader could be removed.

The particular scenario I'm most concerned about is if a bug is introduced into one of the auto-loaders it could be very difficult to detect if someone's particular setup is using the other auto-loader.

Thanks as always for sharing your work with the community. Cheers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions