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

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

Offen
  • Stimmt etwas nicht?
#4,376 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
8/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
react, react-native, typescript
Bereich
build-system, release, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1.4k
Forks
179
Ø Merge
2 T. 23 Min.
Gemergte PRs (30 T.)
33

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.