chore: use *ENABLED instead of *DISABLED for constant

sanity-io · Oct 1, 2024 · 011610c · 011610c
1 parent 22e1ac9
commit 011610c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/packages/sanity/src/_internal/cli/actions/manifest/extractManifestAction.ts b/packages/sanity/src/_internal/cli/actions/manifest/extractManifestAction.ts
@@ -20,7 +20,7 @@ const SCHEMA_FILENAME_SUFFIX = '.create-schema.json'
 
 /** Escape-hatch env flags to change action behavior */
 const FEATURE_ENABLED_ENV_NAME = 'SANITY_CLI_EXTRACT_MANIFEST_ENABLED'
-const EXTRACT_MANIFEST_DISABLED = process.env[FEATURE_ENABLED_ENV_NAME] === 'false'
+const EXTRACT_MANIFEST_ENABLED = process.env[FEATURE_ENABLED_ENV_NAME] !== 'false'
 const EXTRACT_MANIFEST_LOG_ERRORS = process.env.SANITY_CLI_EXTRACT_MANIFEST_LOG_ERRORS === 'true'
 
 const CREATE_TIMER = 'create-manifest'
@@ -44,7 +44,7 @@ export async function extractManifestSafe(
   args: CliCommandArguments<ExtractFlags>,
   context: CliCommandContext,
 ): Promise<Error | undefined> {
-  if (EXTRACT_MANIFEST_DISABLED) {
+  if (!EXTRACT_MANIFEST_ENABLED) {
     return undefined
   }