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

Aberta
#4,317 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
node.js, typescript
Domínio
devtools, mobile-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
5.3k
Forks
377
Merge médio
14h 24min
PRs com merge (30d)
675

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de callstack/agent-device

Todas as issues de callstack/agent-device

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.