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

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

Aperta
  • Qualcosa non va?
#4,376 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
8/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, react-native, typescript
Ambito
build-system, release, tooling

Direzione di ricerca

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.

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

Descrizione

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.

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.