Vlad Durnea
cffdf8af86
Some checks failed
CI/CD Pipeline / unit-tests (push) Failing after 1m16s
CI/CD Pipeline / integration-tests (push) Failing after 2m32s
CI/CD Pipeline / lint (push) Successful in 5m22s
CI/CD Pipeline / e2e-tests (push) Has been skipped
CI/CD Pipeline / build (push) Has been skipped
25 lines
973 B
JavaScript
25 lines
973 B
JavaScript
"use strict";
|
|
|
|
Object.defineProperty(exports, "__esModule", {
|
|
value: true
|
|
});
|
|
exports.GRID_EXPERIMENTAL_ENABLED = void 0;
|
|
// A guide to feature toggling (deprecated)
|
|
//
|
|
// The feature toggle is:
|
|
// - independent from the NODE_ENV
|
|
// - isn't pruning code in production, as the objective is to eventually ship the code.
|
|
// - doesn't allow to cherry-pick which feature to enable
|
|
//
|
|
// By default, the experimental features are only enabled in:
|
|
// - the local environment
|
|
// - the pull request previews
|
|
//
|
|
// Reviewers can force the value with the local storage and the GRID_EXPERIMENTAL_ENABLED key:
|
|
// - 'true' => force it to be enabled
|
|
// - 'false' => force it to be disabled
|
|
//
|
|
// Developers (users) are discouraged to enable the experimental feature by setting the GRID_EXPERIMENTAL_ENABLED env.
|
|
// Instead, prefer exposing experimental APIs, for instance, a prop or a new `unstable_` module.
|
|
|
|
const GRID_EXPERIMENTAL_ENABLED = exports.GRID_EXPERIMENTAL_ENABLED = false; |