Extract HarmonyOS behind a platform plugin interface, then ship it as @agent-device/harmonyos (0.22)

オープン
  • 何か問題がありますか？
#4,317 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
node.js, typescript
領域
devtools, mobile-dev

調査の方向性

Start with the provider plugin registry and ADR 0034, then trace platform and HarmonyOS references in packages/kernel/src/device.ts, packages/kernel/src/contracts.ts, and packages/platform-harmonyos. Define the platform registration interface and move HarmonyOS into @agent-device/harmonyos. Done means the listed commands work with the plugin, selectors give a typed install hint without it, live evidence is committed under docs/evidence/, and an ADR records the interface.

索引モデルが issue の本文から書いたものです。

説明

refactor

Purpose

HarmonyOS is wired into core today. packages/platform-harmonyos is a private package, and harmonyos is hard-coded in packages/kernel/src/device.ts (PLATFORMS) and packages/kernel/src/contracts.ts (SESSION_RUNTIME_PLATFORMS and the harmonyos-instance backend). Every HarmonyOS change therefore lands in core and is reviewed against core, even though CI has no HarmonyOS device or HDC lane to verify it.

Providers already plug in through the provider plugin registry (ADR 0034), and first-party providers ship as plugins: @agent-device/webos, and planned for 0.22 @agent-device/limrun (#3311) and @agent-device/browserstack (#3309). Platforms have no equivalent interface. HarmonyOS should be the first platform to move behind one, in the same 0.22 window as the other extractions under #3747.

Required behavior

Two steps, in order:

  1. Platform plugin interface. A platform registers itself, along with its device kinds, selector flags, session runtime and backend, through a plugin registry like the provider registry, instead of being listed in closed kernel enums. Core keeps one owner for platform admission. Built-in platforms (Apple, Android, Linux, web, Vega) can stay built in; the interface only has to let a platform live outside core.
  2. HarmonyOS as a plugin. Move platform-harmonyos behind that interface and publish it as @agent-device/harmonyos, loaded the way provider plugins are. Remove the HarmonyOS entries from the kernel enums in the same change. Add no compatibility shims; this is a 0.22 break, like the other extractions.

Completion conditions

  • No harmonyos literal remains in packages/kernel outside a test fixture.
  • With the plugin installed, devices, open, snapshot, press and close work on a HarmonyOS device. The live evidence is committed under docs/evidence/, since CI cannot run HarmonyOS.
  • Without the plugin installed, HarmonyOS selectors fail with a typed reason naming the plugin to install.
  • An ADR amendment, or a new ADR next to ADR 0034, records the platform plugin interface.

Dependencies

  • Lands in 0.22, alongside #3747 and #3759.
  • Starts after 0.21.37 ships, matching the existing plugin-extraction hold.
  • Open HarmonyOS feature PRs should land first, or be rebased onto the plugin package once it exists. The order is tracked in the contributor umbrella.
主要言語
TypeScript
スター
5.3k
フォーク
377
平均マージ
13時間 58分
マージ済み PR（30日）
654

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstack/agent-device のほかの issue

callstack/agent-device の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。