Is your feature request related to a problem?
Currently, it is not possible to check whether the current request is from the Customizer.
Describe the desired solution
Add a ->is(WpContext::CUSTOMIZER)/->isCustomizer() check.
Describe the alternatives that you have considered
The Customizer is gradually being replaced by FSE, so it will eventually cease to exist. The question is whether new logic should be introduced for a "legacy" feature.
Additional context
Without this feature, you have to cumbersome check for the Customizer yourself:
global $wp_customize;
if (isset($wp_customize)) {
// do things
}
Code of Conduct
Is your feature request related to a problem?
Currently, it is not possible to check whether the current request is from the Customizer.
Describe the desired solution
Add a
->is(WpContext::CUSTOMIZER)/->isCustomizer()check.Describe the alternatives that you have considered
The Customizer is gradually being replaced by FSE, so it will eventually cease to exist. The question is whether new logic should be introduced for a "legacy" feature.
Additional context
Without this feature, you have to cumbersome check for the Customizer yourself:
Code of Conduct