Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#4,380 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp, csharp, ios, objective-c, react-native, typescript
Bereich
mobile-dev

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1.4k
Forks
180
Ø Merge
1 T. 14 Std.
Gemergte PRs (30 T.)
30

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/fluentui-react-native

Alle Issues in microsoft/fluentui-react-native

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.