You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually – is it really necessary that the bedrock-autoloader is checked in? It's listed as a composer dependency, after all... maybe it's because it doesn't know where it should install itself?
Additional context
No response
The text was updated successfully, but these errors were encountered:
The dependency and that single file are two different things. The single file is the entrypoint and is required due to how WordPress mu plugins work. It creates a new instance of the class provided by the dependency for the actual functionality.
Summary
I just noticed that single-file mu-plugins made it into my version control. This stems from the entry in
.gitignore
:https://github.com/roots/bedrock/blob/c20a9dc02aef36b90ed0c6c51d895ce9fc3edde4/.gitignore#L4C1-L4C22
A more sensible suggestion could be this, if
bedrock-autoloader.php
really needs to be tracked in git:Actually – is it really necessary that the bedrock-autoloader is checked in? It's listed as a composer dependency, after all... maybe it's because it doesn't know where it should install itself?
Additional context
No response
The text was updated successfully, but these errors were encountered: