-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wp-env: add mu-plugins support #22257
Conversation
Size Change: 0 B Total Size: 825 kB ℹ️ View Unchanged
|
09aa5eb
to
5af387f
Compare
Doesn't #22256 remove the need for this? MU Plugins can just go in mappings, and we can keep the schema simple. |
Sure. but why wouldn't we remove plugins and themes in that scenario? If the plugins/themes API is being kept because it's an easy-to-use API and not just for back-compat, then why wouldn't we support mu-plugins in that easy-to-use API as well? Unless we consider mu-plugins more of an advanced use case, I guess. |
MU Plugins are an advanced use case, and they don't need activation. |
Right, how does that relate though? wp-env isn't trying to activate them. I'm definitely fine just using #22256 instead. 🤷 We can always reopen this if people really want mu-plugins as a more simple API. |
Because the main benefit of having explicit |
Ah, I see the argument. |
Description
Adds support to .wp-env.json for mu-plugins. (Accepted sources work the same as themes & plugins.)
How has this been tested?
Locally and with unit tests
Types of changes
New feature
Checklist: