一键在 Manus 中运行任何 Skill

angular-ts-to-js-migration

星标8

分支5

更新时间2026年4月14日 07:10

Rules and workflow for migrating Angular TypeScript components to plain ES module JavaScript for the scripts/ bridge layer

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

pegasystems

pegasystems/constellation-mobile-sdk

下载

When migrating .ts (Angular) components to .js:

Remove all Angular imports, decorators (@Component, @Input), and TypeScript types
Remove interfaces and type annotations
Remove all Angular lifecycle interfaces
For simple fields components extend FieldBaseComponent if possible and reasonable.
For Container components extend ContainerBaseComponent if possible and reasonable.
For rest of components extend BaseComponent
ngOnInit → init() with componentsManager.onComponentAdded(this)
ngOnDestroy → destroy() with super.destroy() and componentsManager.onComponentRemoved(this)
Merge onStateChange into checkAndUpdate()
updateSelf → #updateSelf() (private); add #sendPropsUpdate() at end
Add update(pConn, ...) method for external re-rendering
Replace this.pConn$ → this.pConn; remove all as any casts
Normalize quotes to double quotes
If there is some external dependency try to look in additional provided ts files and copy its content to migrated js. If nothing is found try to find existing equivalent in js files or create mocked implementation.
When migrating parts of code prefer copy-paste over code modification.
Never change logic of migrated components.
In sdk-pega-component-map.js uncomment migrated component entry in pegaSdkComponentMap and also import line. Fix imported component path.

同仓库更多 Skills

同仓库

Rules and workflow for integrating Constellation Mobile SDK into a Compose Multiplatform application

Rules and guidelines for overriding UI field components in the Compose Multiplatform SDK

Rules and guidelines for writing Android instrumented UI tests for the android-cmp-app sample

Rules and guidelines for creating components in the core Kotlin module

Rules and guidelines for writing unit tests for JavaScript components in the scripts/ bridge layer

Rules and guidelines for creating Compose Multiplatform UI components in the ui-components-cmp module

name	angular-ts-to-js-migration
description	Rules and workflow for migrating Angular TypeScript components to plain ES module JavaScript for the scripts/ bridge layer

When migrating .ts (Angular) components to .js:

Remove all Angular imports, decorators (@Component, @Input), and TypeScript types
Remove interfaces and type annotations
Remove all Angular lifecycle interfaces
For simple fields components extend FieldBaseComponent if possible and reasonable.
For Container components extend ContainerBaseComponent if possible and reasonable.
For rest of components extend BaseComponent
ngOnInit → init() with componentsManager.onComponentAdded(this)
ngOnDestroy → destroy() with super.destroy() and componentsManager.onComponentRemoved(this)
Merge onStateChange into checkAndUpdate()
updateSelf → #updateSelf() (private); add #sendPropsUpdate() at end
Add update(pConn, ...) method for external re-rendering
Replace this.pConn$ → this.pConn; remove all as any casts
Normalize quotes to double quotes
If there is some external dependency try to look in additional provided ts files and copy its content to migrated js. If nothing is found try to find existing equivalent in js files or create mocked implementation.
When migrating parts of code prefer copy-paste over code modification.
Never change logic of migrated components.
In sdk-pega-component-map.js uncomment migrated component entry in pegaSdkComponentMap and also import line. Fix imported component path.