Infrastructure: Qualify native-core TurboModule support with a real consumer
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cpp, csharp, ios, objective-c, react-native, typescript
- 领域
- mobile-dev
调研方向
The payload names no source files or tests; the work centres on the FRNNativeCoreSpec boundary and package codegen under packages/agentic/native-core, with the README and AGENTS.md as the packaging rules to read first. Done means a real consumer's TurboModule is invoked and returns results in supported Apple and Windows hosts, not merely generated or mocked. The issue is deferred until a concrete consumer exists and requires design work, so it is not a first contribution.
由索引模型根据 Issue 内容生成。
描述
Goal
Exercise the module half of native-core's FRNNativeCoreSpec boundary with a representative real feature. Part of #4275. This remains deferred until a genuine consumer justifies it; do not create a speculative module merely to share view behavior.
Observed baseline — 2026-10-15
Callout and FocusZone exercise the component path. Package codegen uses type: all and Windows has both component/module generators, but this is not evidence that a real TurboModule works in supported consuming hosts.
Acceptance
- Identify the concrete non-view feature/consumer and review its public platform contract and lifecycle.
- Add the correctly named
Native<Name>.tsschema, thin native module adapters, explicit exports, and a genuine shared service only when reuse exists. Components and modules are peer service consumers; view commands must not route through a global module. - Verify Apple/Windows codegen/provider registration, packed source ownership, errors/cancellation, dispatcher affinity, and cleanup in real consuming hosts and declared renderer/version combinations.
- Preserve Office bridging-header and CocoaPods-module build compatibility, legacy Win32 ownership, and existing component registrations.
- Record actual native invocation/results and unsupported hosts. A generated interface, compilation, or JS mock does not establish module readiness.
Evidence
Retired handoff: b55d6c9a3:packages/agentic/native-core/plans/modernization.md; durable packaging/admission rules in packages/agentic/native-core/README.md and AGENTS.md. Candidate wave-three 5f6e7af1252bcfe087dcd1672afaa4ceb7c5efbb is selective reference material, not qualified module delivery.
- 主要语言
- TypeScript
- 星标
- 1.4k
- 派生
- 179
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 34
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/fluentui-react-native 的其他 Issue
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)可能已有人在做 @UditDewan 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/fluentui-react-native#4174 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 18/100
microsoft/fluentui-react-native#4379 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 5/100
microsoft/fluentui-react-native#4378 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 8/100
microsoft/fluentui-react-native#4377 ·
维护者通常 1 天内回复
-
Infrastructure: Qualify native-core Win32 capabilities, peer floors, publishing, and root admission未关闭
难度 5/5 一周以上 新手友好度 8/100
microsoft/fluentui-react-native#4376 ·
维护者通常 1 天内回复
查看 microsoft/fluentui-react-native 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 75/100
siyuan-note/siyuan#20629 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Volume eject does not refuse system, root or /home mounts可能已有人在做 @bernardopg 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
spacedriveapp/spacedrive#3159 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
melgarafael/DeskcommCRM#3000 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
callstackincubator/simlock#639 ·
维护者通常 1 天内回复