Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#4,380 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, csharp, ios, objective-c, react-native, typescript
Área
mobile-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1.4k
Forks
179
Merge medio
1 d 23 h
PR fusionados (30 d)
34

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/fluentui-react-native

Todos los issues de microsoft/fluentui-react-native

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.