Fix issue with static methods in class autoloader #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
In #158 we added a way to auto-initialise and load classes in the MU plugin and theme.
Because the classfinder uses static methods, it only works on a single application root.
To get around this, we need to manually set the application root before we look for classes in a namespace, so that it can find the right composer.json file
This has been tested on a client project that's using this version of the scaffold.
How to test the Change
Changelog Entry
Checklist: