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

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

Abierto
  • ¿Algo no está bien?
#4,376 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
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, react-native, typescript
Área
build-system, release, tooling

Línea de trabajo

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.

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

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1.4k
Forks
180
Merge medio
2 d 23 min
PR fusionados (30 d)
33

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.