Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#4,376 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
react, react-native, typescript

调研方向

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
派生
179
平均合并
1 天 23 小时
30 天内合并 PR
34

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/fluentui-react-native 的其他 Issue

查看 microsoft/fluentui-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。