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

Components: Generate Menu

Aperta
  • Qualcosa non va?
#4,232 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
react-native, typescript
Ambito
frontend

Direzione di ricerca

Inizia da packages/agentic/components/specs/menu/SPEC.md e dai relativi file di specifica, poi leggi src/components/AGENTS.md e le implementazioni esistenti di menu-item e divider. Controlla le dipendenze di popover e focus-zone prima di scegliere il comportamento del menu; per considerare il lavoro completato servono la struttura completa di src/components/menu, test e stories colocalizzati, la validazione della piattaforma, export espliciti da index.ts, un changeset e prove della sua prontezza.

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

Descrizione

Summary

Deliver Menu as an original reviewed React Native component contract, implementation, public export, and evidence-backed desktop behavior. Parent: #4273.

Current state - 2026-10-02 (UTC)

Observed: Audited against main at 75c55923873124201d2ffbf3b3e67960047bd481. There is no implemented/exported menu component or colocated contract on main. This generation issue remains open.

Assessment: Popover plus collection behavior.

Dependencies and next action

Popover #4236 is missing; MenuItem, Divider, Fabric FocusZone, and shared native focus targets are delivered.

Start with the component's source-backed native contract review. A missing local contract is work to author, not a reason to wait for the completed #4252. Only the named unresolved component/host/product decisions above remain prerequisites; do not carry forward blanket overlay-wave or missing-Fabric blockers.

Component scope

  • Compose popup hosting with MenuItem/Divider content and keep item actions/selection separate from menu open state.
  • Own roving focus, Home/End, type-ahead, Escape/dismiss/return focus, and submenu open/close policy.
  • Review submenu scope and nested positioning explicitly; select a permitted focus-composition path and qualify real native focus/announcements.

Non-goals

Do not migrate legacy consumers, add mobile support, copy private/web source prose into the public package, or rewrite unrelated component APIs. Desktop V1 Win32/Windows/macOS behavior is compatibility evidence, not an iOS canonical baseline. Keep shared hosting, icons, and focus ownership in their named tasks.

Delivery and acceptance

  • Author an original colocated SPEC.md and spec/ companions with schema-version-2 sources[], requirement IDs, source authority, and explicit native divergences; pass pre-code contract review before implementation.
  • Implement the typed state/style/render/assembly stages, finite variant axes, optional slots, native root refs, user-prop/style forwarding, and explicit package exports covered by src/index.test.ts. Preserve React 19 ref props, shared focus policy, theme-only style caching, disabled-over-pressed-over-hovered precedence, and repository source boundaries.
  • Add runtime and compile-time coverage for public API, every finite axis, optional content, accessibility, disabled state, constrained layout, and each controlled/uncontrolled or externally selected state path.
  • Add representative and stress stories with top-level executable wdio cases. Use the delivered Storybook/native assertion infrastructure (#4255, #4256); record actual Windows/macOS results and Win32 compatibility evidence, with capability skips stated rather than counted as passes.
  • Run owning-workspace format, lint, build, and tests, plus Windows/macOS Storybook bundles; run the root build for changed public types/exports/manifests and add a changeset for package changes. Record a readiness level with its evidence under #4216 and #4251.
  • Merge the reviewed implementation before closing this generation issue. Source contracts, branch code, successful bundling, or a closed unmerged PR alone do not establish delivered readiness.

Contract review is normal phase-one work, not a missing-ingestion blocker. #4252 is complete; the old specs/<name>/blockers.md records are historical evidence, not live authoring inputs.

Current native qualification limits: #4342 tracks all-skipped WDIO selections being reported as passed; inspect executed cases rather than aggregate success. #4343, #4346, and #4347 retain full accessibility, native state projection, and focus-regression qualification. #4344 tracks native catalog crash exclusions, and #4349 tracks qualifying/promoting required CI. These are evidence/readiness gates, not a claim that delivered test infrastructure or every component behavior is missing.

Evidence

Evidence reflects this repository snapshot; the checked-in candidate drift report is dated 2026-08-31 and is not a fresh upstream audit.

Lingua principale
TypeScript
Stelle
1.4k
Fork
179
Merge medio
2g 10h
PR unite (30g)
24

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.