Move config error processing for database init

As we add more configuration errors, we can standardize throwing and catching them in the `codeql` file where we actually invoke the commands. Also, rename to `isCliConfigurationError` for more clarity.
github · Jan 30, 2024 · 7837cc7 · 7837cc7
1 parent d678f61
commit 7837cc7
Show file tree

Hide file tree

Showing 9 changed files with 95 additions and 124 deletions.
diff --git a/lib/cli-config-errors.js b/lib/cli-config-errors.js
diff --git a/lib/cli-config-errors.js.map b/lib/cli-config-errors.js.map
diff --git a/lib/codeql.js b/lib/codeql.js
diff --git a/lib/codeql.js.map b/lib/codeql.js.map
diff --git a/lib/init.js b/lib/init.js
diff --git a/lib/init.js.map b/lib/init.js.map
diff --git a/src/cli-config-errors.ts b/src/cli-config-errors.ts
@@ -51,7 +51,7 @@ export const cliErrorsConfig: Record<
  * error: if there is an exit code, this takes precedence. Otherwise, matches
  * the error message against the expected message snippets.
  */
-export function isConfigurationError(
+export function isCliConfigurationError(
   cliError: CliError,
   cliErrorMessage: string,
   exitCode?: number,