Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Infrastructure: Qualify native-core TurboModule support with a real consumer

Aperta
  • Qualcosa non va?
#4,380 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, csharp, ios, objective-c, react-native, typescript
Ambito
mobile-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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>.ts schema, 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.

Lingua principale
TypeScript
Stelle
1.4k
Fork
179
Merge medio
1g 23h
PR unite (30g)
34

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/fluentui-react-native

Tutte le issue di microsoft/fluentui-react-native

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.