Description

Allows the user to change the options for any WordPress environment in wp-env separately. This refactors the way the config works internally by putting all service-level configuration options into env.<service>.

Note: One subtle difference with parsing behavior is that wp-config values are now merged instead of overwritten.

For example:

const parsedConfig = {
  ...uniqueOptions, // like dockerComposeConfigPath, workDirectoryPath, etc)
  env {
    development: WPServiceConfig,
    tests: WPServiceConfig,
  },
}

WPServiceConfig is just something like:

const defaultEnvConfig = {
	core: null,
	plugins: [],
	themes: [],
	port: 8888,
	config: {
		WP_DEBUG: true,
		SCRIPT_DEBUG: true,
		WP_TESTS_DOMAIN: 'localhost',
	},
	mappings: {},
};

the WPServiceConfig contains all options applicable to the service. For example, if .wp-env.json looks like:

{
  "plugins": [ "./" ],
  "env": {
    "tests": {
      "themes": [ "./some-theme" ]
    }
  }
}

the config will be merged like so:

const config = {
  // ... common config options, like workDir
  env: {
    development: {
      // ... other service-level options like port
      plugins: [ "./" ],
      themes: [],
    },
    tests: {
      // ... other service-level options like port
      plugins: [ "./" ],
      themes: [ "./some-theme" ],
    },
  },
}

As you can see, the base-level plugins option is added to both development and tests.

Practically, in .wp-env.json, the only thing that changes is that you can override any of the existing options inside of env.development or env.tests.

Todo:

• Fix wp-env unit tests
• Update Travis config which was working around this issue

How has this been tested?

Unit tests, travis, and local testing in my own environment

Types of changes

new feature/refactor

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

closes #22514