@salesforce/plugin-deploy-retrieve 1.8.5-beta.2 → 1.8.5-beta.3

package/messages/convert.mdapi.md

@@ -28,7 +28,7 @@ the output directory to store the source–formatted files
 
 file path to manifest (package.xml) of metadata types to convert.
 
-# flags.metadata-path
+# flags.metadata-dir
 
 comma-separated list of metadata file paths to convert
 
@@ -48,9 +48,9 @@ The directory to store your files in after they’re converted to the source for
 
 - The complete path to the manifest (package.xml) file that specifies the metadata types to convert.
 
-- If you specify this parameter, don’t specify --metadata or --source-path.
+- If you specify this parameter, don’t specify --metadata or --source-dir.
 
-# flagsLong.metadata-path
+# flagsLong.metadata-dir
 
 - A comma-separated list of paths to the local metadata files to convert. The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).
 

package/messages/convert.source.md

@@ -35,7 +35,7 @@ name of the package to associate with the metadata-formatted files
 
 file path to manifest (package.xml) of metadata types to convert.
 
-# flags.source-path
+# flags.source-dir
 
 comma-separated list of paths to the local source files to convert
 
@@ -47,9 +47,9 @@ comma-separated list of metadata component names to convert
 
 - The complete path to the manifest (package.xml) file that specifies the metadata types to convert.
 
-- If you specify this parameter, don’t specify --metadata or --source-path.
+- If you specify this parameter, don’t specify --metadata or --source-dir.
 
-# flagsLong.source-path
+# flagsLong.source-dir
 
 - A comma-separated list of paths to the local source files to convert. The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).
 

package/messages/delete.source.md

@@ -16,7 +16,7 @@ To remove deleted items from scratch orgs, which have change tracking, use "sf p
 
 - $ <%= config.bin %> <%= command.id %> -p path/to/source
 
-# flags.source-path
+# flags.source-dir
 
 comma-separated list of source file paths to delete
 
@@ -70,9 +70,9 @@ verbose output of delete result
 
 - A comma-separated list of names of metadata components to delete from your project and your org.
 
-- If you specify this parameter, don’t specify --source-path.
+- If you specify this parameter, don’t specify --source-dir.
 
-# flagsLong.source-path
+# flagsLong.source-dir
 
 - A comma-separated list of paths to the local metadata to delete. The supplied paths can be a single file (in which case the operation is applied to only one file) or a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).
 

package/messages/manifest.create.md

@@ -1,7 +1,7 @@
 # description
 
 create a project manifest that lists the metadata components you want to deploy or retrieve
-Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-path). You can specify either of these parameters, not both.
+Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these parameters, not both.
 
 Use --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:
 
@@ -20,7 +20,7 @@ Use --manifest-name to specify a custom name for the generated manifest if the p
 
 - $ <%= config.bin %> <%= command.id %> -m ApexClass:MyApexClass --manifest-type destroy
 
-- $ <%= config.bin %> <%= command.id %> --source-path force-app --manifest-name myNewManifest
+- $ <%= config.bin %> <%= command.id %> --source-dir force-app --manifest-name myNewManifest
 
 - $ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked
 
@@ -44,7 +44,7 @@ name of a custom manifest file to create
 
 directory to save the created manifest
 
-# flags.source-path
+# flags.source-dir
 
 comma-separated list of paths to the local source files to include in the manifest
 

package/oclif.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.8.5-beta.2",
+  "version": "1.8.5-beta.3",
   "commands": {
     "deploy": {
       "id": "deploy",
@@ -105,12 +105,12 @@
           "type": "option",
           "char": "x",
           "summary": "file path to manifest (package.xml) of metadata types to convert.",
-          "description": "The complete path to the manifest (package.xml) file that specifies the metadata types to convert.\nIf you specify this parameter, don’t specify --metadata or --source-path.",
+          "description": "The complete path to the manifest (package.xml) file that specifies the metadata types to convert.\nIf you specify this parameter, don’t specify --metadata or --source-dir.",
           "multiple": false,
           "deprecateAliases": true
         },
-        "metadata-path": {
-          "name": "metadata-path",
+        "metadata-dir": {
+          "name": "metadata-dir",
           "type": "option",
           "char": "p",
           "summary": "comma-separated list of metadata file paths to convert",
@@ -135,7 +135,7 @@
           "multiple": true,
           "exclusive": [
             "manifest",
-            "metadatapath"
+            "metadata-dir"
           ],
           "deprecateAliases": true,
           "delimiter": ","
@@ -206,7 +206,7 @@
           "char": "d",
           "summary": "output directory to store the Metadata API–formatted files in",
           "multiple": false,
-          "default": "metadataPackage_1679527716679",
+          "default": "metadataPackage_1679597528416",
           "deprecateAliases": true,
           "aliases": [
             "outputdir"
@@ -227,13 +227,13 @@
           "name": "manifest",
           "type": "option",
           "char": "x",
-          "summary": "The complete path to the manifest (package.xml) file that specifies the metadata types to convert.\nIf you specify this parameter, don’t specify --metadata or --source-path.",
+          "summary": "The complete path to the manifest (package.xml) file that specifies the metadata types to convert.\nIf you specify this parameter, don’t specify --metadata or --source-dir.",
           "description": "file path to manifest (package.xml) of metadata types to convert.",
           "multiple": false,
           "deprecateAliases": true
         },
-        "source-path": {
-          "name": "source-path",
+        "source-dir": {
+          "name": "source-dir",
           "type": "option",
           "char": "p",
           "summary": "A comma-separated list of paths to the local source files to convert. The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).\nIf you specify this parameter, don’t specify --manifest or --metadata.",
@@ -358,6 +358,7 @@
           "multiple": false,
           "options": [
             "NoTestRun",
+            "RunSpecifiedTests",
             "RunLocalTests",
             "RunAllTestsInOrg"
           ],
@@ -383,13 +384,13 @@
           "type": "option",
           "char": "m",
           "summary": "comma-separated list of names of metadata components to delete",
-          "description": "A comma-separated list of names of metadata components to delete from your project and your org.\nIf you specify this parameter, don’t specify --source-path.",
+          "description": "A comma-separated list of names of metadata components to delete from your project and your org.\nIf you specify this parameter, don’t specify --source-dir.",
           "multiple": true,
           "deprecateAliases": true,
           "delimiter": ","
         },
-        "source-path": {
-          "name": "source-path",
+        "source-dir": {
+          "name": "source-dir",
           "type": "option",
           "char": "p",
           "summary": "comma-separated list of source file paths to delete",
@@ -1674,8 +1675,8 @@
     },
     "project:manifest:create": {
       "id": "project:manifest:create",
-      "summary": "create a project manifest that lists the metadata components you want to deploy or retrieve\nCreate a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-path). You can specify either of these parameters, not both.\n\nUse --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:\n\npackage : package.xml (default)\npre : destructiveChangesPre.xml\npost : destructiveChangesPost.xml\ndestroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.",
-      "description": "create a project manifest that lists the metadata components you want to deploy or retrieve\nCreate a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-path). You can specify either of these parameters, not both.\n\nUse --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:\n\npackage : package.xml (default)\npre : destructiveChangesPre.xml\npost : destructiveChangesPost.xml\ndestroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.",
+      "summary": "create a project manifest that lists the metadata components you want to deploy or retrieve\nCreate a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these parameters, not both.\n\nUse --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:\n\npackage : package.xml (default)\npre : destructiveChangesPre.xml\npost : destructiveChangesPost.xml\ndestroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.",
+      "description": "create a project manifest that lists the metadata components you want to deploy or retrieve\nCreate a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these parameters, not both.\n\nUse --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:\n\npackage : package.xml (default)\npre : destructiveChangesPre.xml\npost : destructiveChangesPost.xml\ndestroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -1686,7 +1687,7 @@
       "examples": [
         "$ <%= config.bin %> <%= command.id %> -m ApexClass",
         "$ <%= config.bin %> <%= command.id %> -m ApexClass:MyApexClass --manifest-type destroy",
-        "$ <%= config.bin %> <%= command.id %> --source-path force-app --manifest-name myNewManifest",
+        "$ <%= config.bin %> <%= command.id %> --source-dir force-app --manifest-name myNewManifest",
         "$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked"
       ],
       "deprecateAliases": true,
@@ -1728,8 +1729,8 @@
           "deprecateAliases": true,
           "delimiter": ","
         },
-        "source-path": {
-          "name": "source-path",
+        "source-dir": {
+          "name": "source-dir",
           "type": "option",
           "char": "p",
           "description": "comma-separated list of paths to the local source files to include in the manifest",

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-deploy-retrieve",
     "description": "deploy and retrieve commands for sf",
-    "version": "1.8.5-beta.2",
+    "version": "1.8.5-beta.3",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "dependencies": {
@@ -10,7 +10,7 @@
         "@salesforce/core": "^3.34.3",
         "@salesforce/kit": "^1.9.2",
         "@salesforce/sf-plugins-core": "^2.2.5",
-        "@salesforce/source-deploy-retrieve": "^7.12.2",
+        "@salesforce/source-deploy-retrieve": "^7.13.0",
         "@salesforce/source-tracking": "^2.2.22",
         "chalk": "^4.1.2",
         "fs-extra": "^10.0.1",
@@ -21,7 +21,7 @@
         "@oclif/plugin-command-snapshot": "^3.3.9",
         "@salesforce/cli-plugins-testkit": "^3.2.25",
         "@salesforce/dev-config": "^3.1.0",
-        "@salesforce/dev-scripts": "^4.1.2",
+        "@salesforce/dev-scripts": "^4.1.3",
         "@salesforce/plugin-command-reference": "^2.4.1",
         "@salesforce/plugin-functions": "^1.17.4",
         "@salesforce/plugin-settings": "^1.4.2",
@@ -171,7 +171,7 @@
             "command": "tsc -p . --pretty --incremental",
             "files": [
                 "src/**/*.ts",
-                "tsconfig.json",
+                "**/tsconfig.json",
                 "messages/**"
             ],
             "output": [
@@ -197,7 +197,8 @@
                 "src/**/*.ts",
                 "test/**/*.ts",
                 "messages/**",
-                ".eslint*"
+                "**/.eslint*",
+                "**/tsconfig.json"
             ],
             "output": []
         },
@@ -205,8 +206,7 @@
             "command": "tsc -p \"./test\" --pretty",
             "files": [
                 "test/**/*.ts",
-                "tsconfig.json",
-                "test/tsconfig.json"
+                "**/tsconfig.json"
             ],
             "output": []
         },
@@ -228,9 +228,8 @@
             "files": [
                 "test/**/*.ts",
                 "src/**/*.ts",
-                "tsconfig.json",
+                "**/tsconfig.json",
                 ".mocha*",
-                "test/tsconfig.json",
                 "!*.nut.ts",
                 ".nycrc"
             ],
@@ -267,7 +266,7 @@
         }
     },
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.2.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.2.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.3.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.3.sig"
     }
 }