diff options
author | Felix Arntz <flixos90@git.wordpress.org> | 2023-06-26 19:55:28 +0000 |
---|---|---|
committer | Felix Arntz <flixos90@git.wordpress.org> | 2023-06-26 19:55:28 +0000 |
commit | 4a16702090984caef24af5a07d598cc5afff2fdc (patch) | |
tree | bfffbbff18955fd882371cd925b6453cc9b4a959 /tools | |
parent | 88de9a9d8efe13a21ebdcdfbf6f87d78875c8f0e (diff) | |
download | wordpress-4a16702090984caef24af5a07d598cc5afff2fdc.tar.gz wordpress-4a16702090984caef24af5a07d598cc5afff2fdc.zip |
General: Introduce `WP_DEVELOPMENT_MODE` constant to signify context-specific development mode.
In recent releases, WordPress core added several instances of cache usage around specific files. While those caches are safe to use in a production context, in development certain nuances apply for whether or not those caches make sense to use. Initially, `WP_DEBUG` was used as a temporary workaround, but it was clear that a more granular method to signify a specific development mode was required: For example, caches around `theme.json` should be disabled when working on a theme as otherwise it would disrupt the theme developer's workflow, but when working on a plugin or WordPress core, this consideration does not apply.
This changeset introduces a `WP_DEVELOPMENT_MODE` constant which, for now, can be set to either "core", "plugin", "theme", or an empty string, the latter of which means no development mode, which is also the default. A new function `wp_get_development_mode()` is the recommended way to retrieve that configuration value.
With the new function available, this changeset replaces all existing instances of the aforementioned `WP_DEBUG` workaround to use `wp_get_development_mode()` with a more specific check.
Props azaozz, sergeybiryukov, peterwilsoncc, spacedmonkey.
Fixes #57487.
git-svn-id: https://develop.svn.wordpress.org/trunk@56042 602fd350-edb4-49c9-b593-d223f7449a82
Diffstat (limited to 'tools')
-rw-r--r-- | tools/local-env/scripts/install.js | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/local-env/scripts/install.js b/tools/local-env/scripts/install.js index c17bbce887..e8a448c8c9 100644 --- a/tools/local-env/scripts/install.js +++ b/tools/local-env/scripts/install.js @@ -16,6 +16,7 @@ wp_cli( `config set WP_DEBUG_LOG ${process.env.LOCAL_WP_DEBUG_LOG} --raw --type= wp_cli( `config set WP_DEBUG_DISPLAY ${process.env.LOCAL_WP_DEBUG_DISPLAY} --raw --type=constant` ); wp_cli( `config set SCRIPT_DEBUG ${process.env.LOCAL_SCRIPT_DEBUG} --raw --type=constant` ); wp_cli( `config set WP_ENVIRONMENT_TYPE ${process.env.LOCAL_WP_ENVIRONMENT_TYPE} --type=constant` ); +wp_cli( `config set WP_DEVELOPMENT_MODE ${process.env.LOCAL_WP_DEVELOPMENT_MODE} --type=constant` ); // Move wp-config.php to the base directory, so it doesn't get mixed up in the src or build directories. renameSync( 'src/wp-config.php', 'wp-config.php' ); |