fix: dont use Messages for configMeta

salesforcecli · Nov 8, 2023 · a4d33a2 · a4d33a2
1 parent 46c3625
commit a4d33a2
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 13 deletions.
diff --git a/messages/config.md b/messages/config.md
diff --git a/src/configMeta.ts b/src/configMeta.ts
@@ -5,10 +5,7 @@
  * For full license text, see LICENSE.txt file in the repo root or https://opensource.org/licenses/BSD-3-Clause
  */
 
-import { ConfigValue, Messages } from '@salesforce/core';
-
-Messages.importMessagesDirectory(__dirname);
-const messages = Messages.loadMessages('@salesforce/plugin-deploy-retrieve', 'config');
+import type { ConfigValue } from '@salesforce/core';
 
 export enum ConfigVars {
   /**
@@ -20,11 +17,12 @@ export enum ConfigVars {
 export default [
   {
     key: ConfigVars.ORG_METADATA_REST_DEPLOY,
-    description: messages.getMessage(ConfigVars.ORG_METADATA_REST_DEPLOY),
+    // @salesforce/core's Messages class is not used here because it's an expensive import to be used in an init hook
+    description: 'Whether deployments use the Metadata REST API (true) or SOAP API (false, default value).',
     hidden: true,
     input: {
       validator: (value: ConfigValue): boolean => typeof value === 'string' && ['true', 'false'].includes(value),
-      failedMessage: messages.getMessage('error.invalidBooleanConfigValue'),
+      failedMessage: 'The config value can only be set to true or false',
     },
   },
 ];