@teambit/harmony.content.cli-reference 1.95.43 → 1.95.44

package/cli-reference.json

@@ -1458,7 +1458,7 @@
     "skipWorkspace": true
   },
   {
-    "name": "import [component-ids...]",
+    "name": "import [component-patterns...]",
     "alias": "",
     "options": [
       [
@@ -1532,15 +1532,15 @@
         "relevant for fetching all components objects. avoid optimizations, fetch all history versions, always"
       ]
     ],
-    "description": "import components from remote scopes to the local workspace",
+    "description": "import components from their remote scopes to the local workspace",
     "extendedDescription": "https://bit.dev/docs/components/importing-components\nyou can use a pattern for multiple ids, such as bit import \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
     "group": "collaborate",
     "private": false,
     "remoteOp": true,
     "arguments": [
       {
-        "name": "component-ids...",
-        "description": "a list of component IDs (separated by space) to import"
+        "name": "component-patterns...",
+        "description": "component IDs or component patterns (separated by space). Use patterns to import groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
       }
     ]
   },
@@ -3121,7 +3121,7 @@
     "remoteOp": true
   },
   {
-    "name": "export [component-names...]",
+    "name": "export [component-patterns...]",
     "alias": "e",
     "options": [
       [
@@ -3132,12 +3132,12 @@
       [
         "a",
         "all",
-        "export all components, including non-staged"
+        "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
       ],
       [
         "",
         "all-versions",
-        "export not only staged versions but all of them"
+        "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
       ],
       [
         "",
@@ -3167,8 +3167,8 @@
     "remoteOp": true,
     "arguments": [
       {
-        "name": "component-names...",
-        "description": "a list of component names or component IDs (separated by space). By default, all new component versions are exported."
+        "name": "component-patterns...",
+        "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
       }
     ]
   },

package/cli-reference.mdx

@@ -517,13 +517,13 @@ bit export => export all staged components to their current scope, if checked ou
 https://bit.dev/docs/components/exporting-components  
 you can use a pattern for multiple ids, such as bit export remote-scope "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
 
-`bit export [component-names...]`
+`bit export [component-patterns...]`
 
 | **Option**                   | **Option alias** | **Description**                                                                                                                         |
 | ---------------------------- | :--------------: | --------------------------------------------------------------------------------------------------------------------------------------- |
 | `--eject`                    |       `-e`       | replace the exported components with their corresponding packages (to use these components without further maintaining them)            |
-| `--all`                      |       `-a`       | export all components, including non-staged                                                                                             |
-| `--all-versions`             |                  | export not only staged versions but all of them                                                                                         |
+| `--all`                      |       `-a`       | export all components, including non-staged (useful when components in the remote scope are corrupted or missing)                       |
+| `--all-versions`             |                  | export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)                     |
 | `--origin-directly`          |                  | EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!                        |
 | `--resume <string>`          |                  | in case the previous export failed and suggested to resume with an export-id, enter the id                                              |
 | `--ignore-missing-artifacts` |                  | EXPERIMENTAL. don't throw an error when artifact files are missing. not recommended, unless you're sure the artifacts are in the remote |
@@ -604,11 +604,11 @@ you can use a pattern for multiple ids, such as bit export remote-scope "utils/\
 ## import
 
 **Workspace only**: yes  
-**Description**: import components from remote scopes to the local workspace  
+**Description**: import components from their remote scopes to the local workspace  
 https://bit.dev/docs/components/importing-components  
 you can use a pattern for multiple ids, such as bit import "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
 
-`bit import [component-ids...]`
+`bit import [component-patterns...]`
 
 | **Option**                       | **Option alias** | **Description**                                                                                                                                                    |
 | -------------------------------- | :--------------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

package/dist/cli-reference.json

@@ -1458,7 +1458,7 @@
         "skipWorkspace": true
     },
     {
-        "name": "import [component-ids...]",
+        "name": "import [component-patterns...]",
         "alias": "",
         "options": [
             [
@@ -1532,15 +1532,15 @@
                 "relevant for fetching all components objects. avoid optimizations, fetch all history versions, always"
             ]
         ],
-        "description": "import components from remote scopes to the local workspace",
+        "description": "import components from their remote scopes to the local workspace",
         "extendedDescription": "https://bit.dev/docs/components/importing-components\nyou can use a pattern for multiple ids, such as bit import \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
         "group": "collaborate",
         "private": false,
         "remoteOp": true,
         "arguments": [
             {
-                "name": "component-ids...",
-                "description": "a list of component IDs (separated by space) to import"
+                "name": "component-patterns...",
+                "description": "component IDs or component patterns (separated by space). Use patterns to import groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
             }
         ]
     },
@@ -3121,7 +3121,7 @@
         "remoteOp": true
     },
     {
-        "name": "export [component-names...]",
+        "name": "export [component-patterns...]",
         "alias": "e",
         "options": [
             [
@@ -3132,12 +3132,12 @@
             [
                 "a",
                 "all",
-                "export all components, including non-staged"
+                "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
             ],
             [
                 "",
                 "all-versions",
-                "export not only staged versions but all of them"
+                "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
             ],
             [
                 "",
@@ -3167,8 +3167,8 @@
         "remoteOp": true,
         "arguments": [
             {
-                "name": "component-names...",
-                "description": "a list of component names or component IDs (separated by space). By default, all new component versions are exported."
+                "name": "component-patterns...",
+                "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
             }
         ]
     },

package/dist/cli-reference.mdx.js

@@ -1998,7 +1998,7 @@ function MDXContent(_ref) {
     parentName: "p"
   }), "\n", "you can use a pattern for multiple ids, such as bit export remote-scope \"utils/", "*", "\". (wrap the pattern with quotes to avoid collision with shell commands)"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"
-  }, "bit export [component-names...]")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
+  }, "bit export [component-patterns...]")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"
   }, (0, _react2.mdx)("tr", {
     parentName: "thead"
@@ -2049,7 +2049,7 @@ function MDXContent(_ref) {
   }, "-a")), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": null
-  }, "export all components, including non-staged")), (0, _react2.mdx)("tr", {
+  }, "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)")), (0, _react2.mdx)("tr", {
     parentName: "tbody"
   }, (0, _react2.mdx)("td", {
     parentName: "tr",
@@ -2062,7 +2062,7 @@ function MDXContent(_ref) {
   }), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": null
-  }, "export not only staged versions but all of them")), (0, _react2.mdx)("tr", {
+  }, "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)")), (0, _react2.mdx)("tr", {
     parentName: "tbody"
   }, (0, _react2.mdx)("td", {
     parentName: "tr",
@@ -2426,7 +2426,7 @@ function MDXContent(_ref) {
     parentName: "p"
   }), "\n", (0, _react2.mdx)("strong", {
     parentName: "p"
-  }, "Description"), ": import components from remote scopes to the local workspace", (0, _react2.mdx)("br", {
+  }, "Description"), ": import components from their remote scopes to the local workspace", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", (0, _react2.mdx)("a", {
     parentName: "p",
@@ -2435,7 +2435,7 @@ function MDXContent(_ref) {
     parentName: "p"
   }), "\n", "you can use a pattern for multiple ids, such as bit import \"utils/", "*", "\". (wrap the pattern with quotes to avoid collision with shell commands)"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"
-  }, "bit import [component-ids...]")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
+  }, "bit import [component-patterns...]")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"
   }, (0, _react2.mdx)("tr", {
     parentName: "thead"