Skip to content

Latest commit

 

History

History
50 lines (35 loc) · 1.58 KB

experiments.md

File metadata and controls

50 lines (35 loc) · 1.58 KB

Experiments

"Experiments" are what Ember CLI calls Feature Toggle.

They are defined in packages/blueprint-model/utilities/experiments.js. For example:

const availableExperiments = ["CONFIG_CACHING"];

When a new feature is added, all supporting code and tests must be guarded to ensure all tests pass when the feature is enabled or disabled:

const { isExperimentEnabled } = require('@ember-tooling/blueprint-model/utilities/experiments');

// ...snip...
if (isExperimentEnabled('SOME_EXPERIMENT')) {
  ...
} else {
  ...
}

An experiment can be summarized into three different states.

Development

During active development of a feature, it can be enabled by setting the experiments related environment variable ('EMBER_CLI_' + EXPERIMENT_NAME).

For example, to enable the CONFIG_CACHING experiment mentioned in the example above while running tests you would run the following command:

EMBER_CLI_CONFIG_CACHING=true pnpm test

Unsupported

The Ember CLI core team will evaluate each experiment before betas get released. If the experiment is not ready, the entry for the experiment is deleted from packages/blueprint-model/utilities/experiments.js (and therefore disabled).

Supported

Once an experiment has gone through the different stages of beta, and we can confidently say a specific feature from an experiment will be supported, we delete the entry in packages/blueprint-model/utilities/experiments.js and remove the experiment guards (e.g. if (experiments.FOO_BAR) {) from the codebase.