Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Infrastructure: Qualify native-core Win32 capabilities, peer floors, publishing, and root admission

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
8/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
react, react-native, typescript
領域
build-system, release, tooling

調査の方向性

This is multi-host qualification and publishing-policy work, not a starter task. Read packages/agentic/native-core/README.md, AGENTS.md, and src/components/*/SPEC.md for the durable contracts, then the retired plan at commit b55d6c9a3. Done means each acceptance box has recorded Win32 and consuming-host evidence, and codegen:windows --check plus the native-core test suite pass. JS-only checks do not count.

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

説明

Goal

Resolve the packaging and all-host admission gates deferred by native-core modernization. Part of #4275; coordinate component semantics with #4274.

Observed baseline — 2026-10-15

Modern Callout/FocusZone/live-target APIs are platform previews in /macos and /windows, require React 19 and the current native registration, and are not root or /win APIs. The baked Office Win32 host retains /legacy; no new managed fields/commands are dispatched to its registrations. Existing build/source/Node checks do not prove old-peer native compatibility or all-host behavior.

Acceptance

  • Establish a named supported React/RN/fork/renderer matrix, including oldest declared peers, and run consuming native codegen/build/runtime checks before changing peer declarations.
  • Obtain Win32 capability evidence for each mandatory modern operation. Do not infer support or impossibility from missing observation infrastructure, and never send an unverified managed protocol to a baked host.
  • Decide and document publishing/peer floors and platform-preview versus root admission. Preserve legacy aliases, host ownership, and compatibility; do not implicitly raise legacy peer floors.
  • Verify packed archives in consuming hosts: codegen identity/provider registration, native sources/generated artifacts, JS/declarations, shims, commands/events/refs, and no machine-local/intermediate outputs.
  • Admit root or /win exports only after equivalent mandatory behavior is demonstrated on every supported desktop host/version combination. Compile checks, platform previews, and skips do not satisfy admission.
  • Keep the package README, export-map/ownership/type tests, component contracts, and release notes aligned with actual admission evidence.

Evidence

Retired handoff: b55d6c9a3:packages/agentic/native-core/plans/modernization.md. Durable rules/contracts remain in packages/agentic/native-core/README.md, AGENTS.md, and src/components/*/SPEC.md. Run native-core format/lint/build/test, codegen:windows --check, Callout/FocusZone shim tests, publishing/changeset checks, and the consuming native matrix; do not label JS-only checks native qualification.

主要言語
TypeScript
スター
1.4k
フォーク
180
平均マージ
2日 23分
マージ済み PR（30日）
33

環境構築

はじめの一歩

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

microsoft/fluentui-react-native のほかの issue

microsoft/fluentui-react-native の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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