@windypro-rourou/dsh-eda 0.1.4 → 0.1.6

package/skill/guide/error-handling.md

@@ -1,38 +1,38 @@
-# Error Handling
-
-## Disable Extensions and Scripting Systems Globally
-
-When you encounter an exception caused by an extension that prevents you from removing the extension through the normal route (such as corrupted or masked data in the top menu bar, or an uninstall returning an error), you can globally disable the extension and the scripting system by adding the `safetyMode=true` parameter within the URL of the EasyEDA Professional editor:
-
-```diff
-- https://pro.easyeda.com/editor
-+ https://pro.easyeda.com/editor?safetyMode=true
-```
-
-::: tip
-
-If you wish to enter debug mode at the same time, you can add the `cll=debug` parameter again:
-
-```diff
-- https://pro.easyeda.com/editor?safetyMode=true
-+ https://pro.easyeda.com/editor?safetyMode=true&cll=debug
-```
-
-:::
-
-## Remove All Extensions Globally
-
-::: danger
-
-**DANGEROUS!** All your installed extensions and standalone scripts will be removed and cannot be recovered. This method should only be used if a serious error is confirmed to be caused by an extension and cannot be resolved by conventional means.
-
-:::
-
-::: details Thanos mode switch
-
-```diff
-- https://pro.easyeda.com/editor
-+ https://pro.easyeda.com/editor?DANGEROUS_OPERATION_DeleteExtensionStorage=true
-```
-
-:::
+# Error Handling
+
+## Disable Extensions and Scripting Systems Globally
+
+When you encounter an exception caused by an extension that prevents you from removing the extension through the normal route (such as corrupted or masked data in the top menu bar, or an uninstall returning an error), you can globally disable the extension and the scripting system by adding the `safetyMode=true` parameter within the URL of the EasyEDA Professional editor:
+
+```diff
+- https://pro.easyeda.com/editor
++ https://pro.easyeda.com/editor?safetyMode=true
+```
+
+::: tip
+
+If you wish to enter debug mode at the same time, you can add the `cll=debug` parameter again:
+
+```diff
+- https://pro.easyeda.com/editor?safetyMode=true
++ https://pro.easyeda.com/editor?safetyMode=true&cll=debug
+```
+
+:::
+
+## Remove All Extensions Globally
+
+::: danger
+
+**DANGEROUS!** All your installed extensions and standalone scripts will be removed and cannot be recovered. This method should only be used if a serious error is confirmed to be caused by an extension and cannot be resolved by conventional means.
+
+:::
+
+::: details Thanos mode switch
+
+```diff
+- https://pro.easyeda.com/editor
++ https://pro.easyeda.com/editor?DANGEROUS_OPERATION_DeleteExtensionStorage=true
+```
+
+:::

package/skill/guide/extension-json.md

@@ -1,135 +1,135 @@
-# Extension Configuration File
-
-In order to define the properties of an extension and the various functions that an extension can invoke, each extension should have an extension configuration file named `extension.json` in the root directory with the following default contents:
-
-<<< @/private/pro-api-sdk/extension.json{json}
-
-## name <Badge type="tip" text="string" />
-
-Extension name. It can only contain lowercase English characters `a-z`, numbers `0-9`, and underscores `-`, and is `5-30` characters long.
-
-## uuid <Badge type="tip" text="string" />
-
-UUID. A unique ID for the extension that can contain only lowercase English characters `a-z`, numbers `0-9`, and is `32` characters long.
-
-## displayName <Badge type="tip" text="string" />
-
-Display name.
-
-## description <Badge type="tip" text="string" />
-
-Description.
-
-## version <Badge type="tip" text="string" />
-
-Version number. The format is `major.minor.patch`.
-
-## publisher <Badge type="tip" text="string" />
-
-Developer Information.
-
-## engines <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" />
-
-The engine to which the extension applies.
-
-### engines.eda <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
-
-Extended adapted version of EasyEDA Professional (online).
-
-## license <Badge type="tip" text="string" />
-
-Open-source licensing terms. It is recommended to go to [Choose a License](https://choosealicense.com/) to select the appropriate open source license for your project.
-
-## repository <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
-
-Repository information for the source code of the extension.
-
-### repository.type <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
-
-The type of source code repository. Optional values are `extension-store` `git` `mercurial` `svn` `ftp` `github` `gitlab` `gitlab-selfhosted` `gitee` `gitea` `bitbucket` `coding` `gnu-savannah` ` gitbucket` `gogs`.
-
-### repository.url <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
-
-Source code repository URL.
-
-## categories <Badge type="tip" text="string | Array<string>" />
-
-The extension's classification. Optional values are `Schematic` `Symbol` `PCB` `Footprint` `Panel` `Library` `Project` `Other`.
-
-## keywords <Badge type="tip" text="Array<string>" />
-
-Keywords.
-
-## images <Badge type="tip" text="Object" />
-
-Images.
-
-### images.logo <Badge type="tip" text="string" />
-
-Logo. Size `1:1`, PNG/JPEG format. Logos can be drawn using an AI generation tool such as [AutoDraw](https://www.autodraw.com/) and a minimum size of `500×500` is recommended.
-
-### images.banner <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
-
-Banner. Size `64:27`, for presentation of extension's store page, JPEG format.
-
-## homepage <Badge type="tip" text="string" />
-
-Project homepage.
-
-## bugs <Badge type="tip" text="string" />
-
-Vulnerability feedback channel. Please fill in a correct URI.
-
-## activationEvents <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
-
-Extension's activation event.
-
-## entry <Badge type="tip" text="string" />
-
-Entry file. No modification is recommended, it is correctly defined within the SDK.
-
-## dependentExtensions <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
-
-Dependencies on other extensions. Supports the use of 32-bit UUIDs of extensions in the Extension Store (automatic pulling supported), or user-defined extension names (manual upload required).
-
-## headerMenus <Badge type="tip" text="Object" />
-
-The header menu registered when the extension is initialized.
-
-The header menu is currently supported to be configured separately according to the following pages:
-
-```json
-{
-	"headerMenus": {
-		"home": [], // [!code focus:9]
-		"blank": [],
-		"sch": [],
-		"symbol": [],
-		"pcb": [],
-		"footprint": [],
-		"pcbView": [],
-		"panel": [],
-		"panelView": []
-	}
-}
-```
-
-### headerMenus[].id <Badge type="tip" text="string" />
-
-Menu item ID. must be unique.
-
-### headerMenus[].title <Badge type="tip" text="string" />
-
-Menu item title.
-
-### headerMenus[].menuItems <Badge type="tip" text="Object" />
-
-Menu item subitems. Up to two levels of subitems can be nested.
-
-`menuItems` conflicts with `registerFn`, only one of them is allowed to exist in the same level.
-
-### headerMenus[].registerFn <Badge type="tip" text="string" />
-
-Menu associated registered method. The method here is associated with a method exported within the code of this extension, you need to export the specified method as an `ES Module` using `export` and fill in its method name here.
-
-`registerFn` conflicts with `menuItems`, only one of them is allowed to exist in the same level.
+# Extension Configuration File
+
+In order to define the properties of an extension and the various functions that an extension can invoke, each extension should have an extension configuration file named `extension.json` in the root directory with the following default contents:
+
+<<< @/private/easyeda-api-sdk/extension.json{json}
+
+## name <Badge type="tip" text="string" />
+
+Extension name. It can only contain lowercase English characters `a-z`, numbers `0-9`, and underscores `-`, and is `5-30` characters long.
+
+## uuid <Badge type="tip" text="string" />
+
+UUID. A unique ID for the extension that can contain only lowercase English characters `a-z`, numbers `0-9`, and is `32` characters long.
+
+## displayName <Badge type="tip" text="string" />
+
+Display name.
+
+## description <Badge type="tip" text="string" />
+
+Description.
+
+## version <Badge type="tip" text="string" />
+
+Version number. The format is `major.minor.patch`.
+
+## publisher <Badge type="tip" text="string" />
+
+Developer Information.
+
+## engines <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" />
+
+The engine to which the extension applies.
+
+### engines.eda <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
+
+Extended adapted version of EasyEDA Professional (online).
+
+## license <Badge type="tip" text="string" />
+
+Open-source licensing terms. It is recommended to go to [Choose a License](https://choosealicense.com/) to select the appropriate open source license for your project.
+
+## repository <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Repository information for the source code of the extension.
+
+### repository.type <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+The type of source code repository. Optional values are `extension-store` `git` `mercurial` `svn` `ftp` `github` `gitlab` `gitlab-selfhosted` `gitee` `gitea` `bitbucket` `coding` `gnu-savannah` ` gitbucket` `gogs`.
+
+### repository.url <Badge type="tip" text="string" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Source code repository URL.
+
+## categories <Badge type="tip" text="string | Array<string>" />
+
+The extension's classification. Optional values are `Schematic` `Symbol` `PCB` `Footprint` `Panel` `Library` `Project` `Other`.
+
+## keywords <Badge type="tip" text="Array<string>" />
+
+Keywords.
+
+## images <Badge type="tip" text="Object" />
+
+Images.
+
+### images.logo <Badge type="tip" text="string" />
+
+Logo. Size `1:1`, PNG/JPEG format. Logos can be drawn using an AI generation tool such as [AutoDraw](https://www.autodraw.com/) and a minimum size of `500×500` is recommended.
+
+### images.banner <Badge type="tip" text="string" /> <Badge type="warning" text="feature" />
+
+Banner. Size `64:27`, for presentation of extension's store page, JPEG format.
+
+## homepage <Badge type="tip" text="string" />
+
+Project homepage.
+
+## bugs <Badge type="tip" text="string" />
+
+Vulnerability feedback channel. Please fill in a correct URI.
+
+## activationEvents <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Extension's activation event.
+
+## entry <Badge type="tip" text="string" />
+
+Entry file. No modification is recommended, it is correctly defined within the SDK.
+
+## dependentExtensions <Badge type="tip" text="Object" /> <Badge type="warning" text="feature" /> <Badge type="info" text="in working" />
+
+Dependencies on other extensions. Supports the use of 32-bit UUIDs of extensions in the Extension Store (automatic pulling supported), or user-defined extension names (manual upload required).
+
+## headerMenus <Badge type="tip" text="Object" />
+
+The header menu registered when the extension is initialized.
+
+The header menu is currently supported to be configured separately according to the following pages:
+
+```json
+{
+	"headerMenus": {
+		"home": [], // [!code focus:9]
+		"blank": [],
+		"sch": [],
+		"symbol": [],
+		"pcb": [],
+		"footprint": [],
+		"pcbView": [],
+		"panel": [],
+		"panelView": []
+	}
+}
+```
+
+### headerMenus[].id <Badge type="tip" text="string" />
+
+Menu item ID. must be unique.
+
+### headerMenus[].title <Badge type="tip" text="string" />
+
+Menu item title.
+
+### headerMenus[].menuItems <Badge type="tip" text="Object" />
+
+Menu item subitems. Up to two levels of subitems can be nested.
+
+`menuItems` conflicts with `registerFn`, only one of them is allowed to exist in the same level.
+
+### headerMenus[].registerFn <Badge type="tip" text="string" />
+
+Menu associated registered method. The method here is associated with a method exported within the code of this extension, you need to export the specified method as an `ES Module` using `export` and fill in its method name here.
+
+`registerFn` conflicts with `menuItems`, only one of them is allowed to exist in the same level.

package/skill/guide/extensions-marketplace.md

@@ -1,61 +1,61 @@
-# Extensions Marketplace
-
-EasyEDA Extensions Marketplace site [https://jlcext.com](https://jlcext.com), which is a professional platform for users to download and share extensions.
-
-If you want to learn how to develop extensions, please refer to the [how-to-start](./how-to-start), which describes in detail how to install the development environment and build your own EasyEDA Pro extension from scratch.
-
-## Publishing Your Extension
-
-When you have fully verified the functionality of the extension you have developed and wish to share it with other users, please visit the [EasyEDA Extensions Marketplace](https://jlcext.com/) and click the **Extension Management** button in the upper right corner:
-
-![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260617_210219.jpg)
-
-
-Enter the extension management page, which supports uploading, publishing and versioning of extensions.
-
-Click the **Extension Upload** button to upload your first extension that meets the following requirements:
-
-1. The extension `extension.json` should contain the following attributes: `name`, `uuid`, `displayName`, `description`, `version`, and `license`;
-2. select and fill in at least one or more of the required extension types (`categories`);
-3. the extension must provide a custom icon and must not use the default `logo` provided in the SDK, the recommended icon size ratio is `1:1`, the format must be PNG or JPEG, the content must be clear without risk of infringement, and the file size must not exceed `5 MiB`;
-4. make sure that the entry file (`entry`) of the extension exists and is valid;
-5. the value of the `name` attribute must not be duplicated across extensions with different `uuid`;
-6. include a detailed description of the extension's functionality and usage in the `README.md` file;
-7. if necessary, keep an change log for the extension in the `CHANGELOG.md` file;
-8. the extension **DOESN'T** contain private information, such as your phone numbers.
-
-![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260603_163928.png)
-
-Select your compiled `.eext` file in the upload pop-up window and upload it. The first uploaded extension will automatically create a namespace into which all subsequent uploads of the extension (identified by `uuid`) will be grouped.
-
-You can view the extension's name, description, version, install count, updated time, and other information on the namespace cover:
-
-![图 4](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172246.png)
-
-
-After the extension is uploaded, it will automatically enter the review process. After approval, it will be listed in the marketplace:
-
-![图 5](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172309.png)
-
-
-After waiting for the review to complete, the review status will change to **Passed**. If there is a case that the review is not passed, please check the reason in the message notification in time and check the non-compliant content in the extension:
-
-![图 6](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172321.png)
-
-After approval, other users will be able to view your extension details and download the uploaded version:
-
-![图 7](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172403.png)
-
-You can view the extension's detail page, where the `README.md` and `CHANGELOG.md` contents of the extension file will be displayed:
-
-![图 8](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172447.png)
-
-All published versions of the extension are listed in the history:
-
-![图 9](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172548.png)
-
-You can leave ratings and reviews of the extension in the comments section:
-
-![图 10](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172603.png)
-
-You can also downgrade the namespace of an extension at any time on the extension management page. This does not affect the status of uploaded versions, and you can also individually unpublish a specific version in the versioning management.
+# Extensions Marketplace
+
+EasyEDA Extensions Marketplace site [https://jlcext.com](https://jlcext.com), which is a professional platform for users to download and share extensions.
+
+If you want to learn how to develop extensions, please refer to the [how-to-start](./how-to-start), which describes in detail how to install the development environment and build your own EasyEDA Pro extension from scratch.
+
+## Publishing Your Extension
+
+When you have fully verified the functionality of the extension you have developed and wish to share it with other users, please visit the [EasyEDA Extensions Marketplace](https://jlcext.com/) and click the **Extension Management** button in the upper right corner:
+
+![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260617_210219.jpg)
+
+
+Enter the extension management page, which supports uploading, publishing and versioning of extensions.
+
+Click the **Extension Upload** button to upload your first extension that meets the following requirements:
+
+1. The extension `extension.json` should contain the following attributes: `name`, `uuid`, `displayName`, `description`, `version`, and `license`;
+2. select and fill in at least one or more of the required extension types (`categories`);
+3. the extension must provide a custom icon and must not use the default `logo` provided in the SDK, the recommended icon size ratio is `1:1`, the format must be PNG or JPEG, the content must be clear without risk of infringement, and the file size must not exceed `5 MiB`;
+4. make sure that the entry file (`entry`) of the extension exists and is valid;
+5. the value of the `name` attribute must not be duplicated across extensions with different `uuid`;
+6. include a detailed description of the extension's functionality and usage in the `README.md` file;
+7. if necessary, keep an change log for the extension in the `CHANGELOG.md` file;
+8. the extension **DOESN'T** contain private information, such as your phone numbers.
+
+![图 0](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260603_163928.png)
+
+Select your compiled `.eext` file in the upload pop-up window and upload it. The first uploaded extension will automatically create a namespace into which all subsequent uploads of the extension (identified by `uuid`) will be grouped.
+
+You can view the extension's name, description, version, install count, updated time, and other information on the namespace cover:
+
+![图 4](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172246.png)
+
+
+After the extension is uploaded, it will automatically enter the review process. After approval, it will be listed in the marketplace:
+
+![图 5](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172309.png)
+
+
+After waiting for the review to complete, the review status will change to **Passed**. If there is a case that the review is not passed, please check the reason in the message notification in time and check the non-compliant content in the extension:
+
+![图 6](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172321.png)
+
+After approval, other users will be able to view your extension details and download the uploaded version:
+
+![图 7](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172403.png)
+
+You can view the extension's detail page, where the `README.md` and `CHANGELOG.md` contents of the extension file will be displayed:
+
+![图 8](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172447.png)
+
+All published versions of the extension are listed in the history:
+
+![图 9](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172548.png)
+
+You can leave ratings and reviews of the extension in the comments section:
+
+![图 10](/storage/images/en/api/guide/extensions-marketplace/extensions-marketplace_20260702_172603.png)
+
+You can also downgrade the namespace of an extension at any time on the extension management page. This does not affect the status of uploaded versions, and you can also individually unpublish a specific version in the versioning management.