@teambit/harmony.content.cli-reference 1.95.109 → 1.95.111

package/cli-reference.json

@@ -420,41 +420,6 @@
     "group": "ungrouped",
     "private": true
   },
-  {
-    "name": "add [path...]",
-    "alias": "a",
-    "options": [
-      [
-        "i",
-        "id <name>",
-        "manually set component id"
-      ],
-      [
-        "m",
-        "main <file>",
-        "define entry point for the components"
-      ],
-      [
-        "n",
-        "namespace <namespace>",
-        "organize component in a namespace"
-      ],
-      [
-        "o",
-        "override <boolean>",
-        "override existing component if exists (default = false)"
-      ],
-      [
-        "s",
-        "scope <string>",
-        "sets the component's scope-name. if not entered, the default-scope will be used"
-      ]
-    ],
-    "description": "Add any subset of files to be tracked as a component(s).",
-    "extendedDescription": "Learn the recommended workflow for tracking directories as components, in the link below.",
-    "group": "development",
-    "private": false
-  },
   {
     "name": "untag [component-name] [component-version]",
     "alias": "",
@@ -1221,6 +1186,41 @@
       }
     ]
   },
+  {
+    "name": "add [path...]",
+    "alias": "a",
+    "options": [
+      [
+        "i",
+        "id <name>",
+        "manually set component id"
+      ],
+      [
+        "m",
+        "main <file>",
+        "define entry point for the components"
+      ],
+      [
+        "n",
+        "namespace <namespace>",
+        "organize component in a namespace"
+      ],
+      [
+        "o",
+        "override <boolean>",
+        "override existing component if exists (default = false)"
+      ],
+      [
+        "s",
+        "scope <string>",
+        "sets the component's scope-name. if not entered, the default-scope will be used"
+      ]
+    ],
+    "description": "Add any subset of files to be tracked as a component(s).",
+    "extendedDescription": "Learn the recommended workflow for tracking directories as components, in the link below.",
+    "group": "development",
+    "private": false
+  },
   {
     "name": "create <template-name> <component-names...>",
     "alias": "",
@@ -2132,6 +2132,11 @@
         "build",
         "EXPERIMENTAL. not needed for now. run the build pipeline in case the feature-flag build-on-ci is enabled"
       ],
+      [
+        "",
+        "editor [editor]",
+        "EXPERIMENTAL. open an editor to write a tag message for each component. optionally, specify the editor-name (defaults to vim)."
+      ],
       [
         "",
         "skip-tests",
@@ -2774,8 +2779,8 @@
           ],
           [
             "",
-            "remote",
-            "relevant when the target-lane locally is differ than the remote and you want the remote"
+            "skip-fetch",
+            "use the current target-lane if exits locally without updating it from the remote"
           ],
           [
             "",
@@ -3750,6 +3755,11 @@
         "",
         "skip-config",
         "do not copy the config (aspects-config) to the new component. helpful when it fails during aspect loading"
+      ],
+      [
+        "",
+        "rename",
+        "rename files and variables/classes according to the new component name"
       ]
     ],
     "description": "EXPERIMENTAL. create a new component out of an existing one (copies source files and config)",

package/cli-reference.mdx

@@ -606,6 +606,7 @@ bit export => export all staged components to their current scope, if checked ou
 | `--refactor`                     |       `-r`       | update the import/require statements in all dependent components (in the same workspace)                  |
 | `--skip-dependency-installation` |                  | do not install packages of the imported components                                                        |
 | `--skip-config`                  |                  | do not copy the config (aspects-config) to the new component. helpful when it fails during aspect loading |
+| `--rename`                       |                  | rename files and variables/classes according to the new component name                                    |
 
 ---
 

package/dist/cli-reference.json

@@ -420,41 +420,6 @@
         "group": "ungrouped",
         "private": true
     },
-    {
-        "name": "add [path...]",
-        "alias": "a",
-        "options": [
-            [
-                "i",
-                "id <name>",
-                "manually set component id"
-            ],
-            [
-                "m",
-                "main <file>",
-                "define entry point for the components"
-            ],
-            [
-                "n",
-                "namespace <namespace>",
-                "organize component in a namespace"
-            ],
-            [
-                "o",
-                "override <boolean>",
-                "override existing component if exists (default = false)"
-            ],
-            [
-                "s",
-                "scope <string>",
-                "sets the component's scope-name. if not entered, the default-scope will be used"
-            ]
-        ],
-        "description": "Add any subset of files to be tracked as a component(s).",
-        "extendedDescription": "Learn the recommended workflow for tracking directories as components, in the link below.",
-        "group": "development",
-        "private": false
-    },
     {
         "name": "untag [component-name] [component-version]",
         "alias": "",
@@ -1221,6 +1186,41 @@
             }
         ]
     },
+    {
+        "name": "add [path...]",
+        "alias": "a",
+        "options": [
+            [
+                "i",
+                "id <name>",
+                "manually set component id"
+            ],
+            [
+                "m",
+                "main <file>",
+                "define entry point for the components"
+            ],
+            [
+                "n",
+                "namespace <namespace>",
+                "organize component in a namespace"
+            ],
+            [
+                "o",
+                "override <boolean>",
+                "override existing component if exists (default = false)"
+            ],
+            [
+                "s",
+                "scope <string>",
+                "sets the component's scope-name. if not entered, the default-scope will be used"
+            ]
+        ],
+        "description": "Add any subset of files to be tracked as a component(s).",
+        "extendedDescription": "Learn the recommended workflow for tracking directories as components, in the link below.",
+        "group": "development",
+        "private": false
+    },
     {
         "name": "create <template-name> <component-names...>",
         "alias": "",
@@ -2132,6 +2132,11 @@
                 "build",
                 "EXPERIMENTAL. not needed for now. run the build pipeline in case the feature-flag build-on-ci is enabled"
             ],
+            [
+                "",
+                "editor [editor]",
+                "EXPERIMENTAL. open an editor to write a tag message for each component. optionally, specify the editor-name (defaults to vim)."
+            ],
             [
                 "",
                 "skip-tests",
@@ -2774,8 +2779,8 @@
                     ],
                     [
                         "",
-                        "remote",
-                        "relevant when the target-lane locally is differ than the remote and you want the remote"
+                        "skip-fetch",
+                        "use the current target-lane if exits locally without updating it from the remote"
                     ],
                     [
                         "",
@@ -3750,6 +3755,11 @@
                 "",
                 "skip-config",
                 "do not copy the config (aspects-config) to the new component. helpful when it fails during aspect loading"
+            ],
+            [
+                "",
+                "rename",
+                "rename files and variables/classes according to the new component name"
             ]
         ],
         "description": "EXPERIMENTAL. create a new component out of an existing one (copies source files and config)",

package/dist/cli-reference.mdx.js

@@ -2449,7 +2449,20 @@ function MDXContent(_ref) {
   }), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": null
-  }, "do not copy the config (aspects-config) to the new component. helpful when it fails during aspect loading")))), (0, _react2.mdx)("hr", null), (0, _react2.mdx)("h2", null, "format"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
+  }, "do not copy the config (aspects-config) to the new component. helpful when it fails during aspect loading")), (0, _react2.mdx)("tr", {
+    parentName: "tbody"
+  }, (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
+  }, "--rename")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": "center"
+  }), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, "rename files and variables/classes according to the new component name")))), (0, _react2.mdx)("hr", null), (0, _react2.mdx)("h2", null, "format"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
     parentName: "p"
   }, "Workspace only"), ": yes", (0, _react2.mdx)("br", {
     parentName: "p"