Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Infrastructure: Restore Storybook stories excluded by native desktop crashes

オープン
  • 何か問題がありますか？
#4,344 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
react-native, typescript
領域
desktop, testing, tooling

調査の方向性

Start with apps/storybook/storybook.config.mts and apps/storybook/README.md, then run the supported yarn storybook ... -- lifecycle with one excluded module at a time. Record the first native failure and story ID for each endpoint, add termination regression coverage, and remove exclusions only when the native cohorts and required checks pass.

索引モデルが issue の本文から書いたものです。

説明

Goal

Restore native Storybook coverage currently excluded because of desktop-host fail-fast crashes. Parent: #4275. Bug follow-up to the delivered endpoint/pipeline milestones #4259/#4256.

Observed state - 2026-10-01

The app's checked-in platform patterns deliberately exclude:

Endpoint Excluded modules
Windows Fabric Accordion and standalone native Callout
Win32 Paper / REX 0.81.1 Accordion and ListItem
macOS None of these modules

The Storybook README documents native fail-fast termination (0xc0000409) as the reason. Current main manifests contain 168 macOS, 158 Windows, and 152 Win32 stories; exclusions are real missing coverage, not equivalent catalogs.

This audit verified source/configuration and generated catalogs, not a new interactive reproduction of each crash. Reproduce against the current resolved forks before attributing a root cause; do not infer that an old runtime diagnosis still explains every endpoint.

Reproduction

On the affected native endpoint, create a minimal isolated fixture or deliberately scoped local catalog for one excluded module at a time. Use the supported yarn storybook ... --<platform> lifecycle from apps/storybook, preserve exact process identity, and retain the first actionable native failure and story ID. Do not remove all exclusions from the normal PR lane before safe per-module qualification.

Acceptance criteria

  • Record a current minimal reproduction, resolved runtime/renderer/OS, first failing story, and native termination/error evidence for each excluded module/endpoint.
  • Fix or consume the owning native/runtime repair without suppressing the crash, replacing the native endpoint, or claiming a render-only proxy as coverage.
  • Add a regression that detects application termination as a failure and exercises the affected behavior, including delayed focus survival where relevant.
  • Remove each platform exclusion only after its native story cohort passes the full owned traversal/tests and cleanup on that endpoint.
  • Manifest/index checks and documentation accurately distinguish any remaining justified exclusions; require a linked issue and reason for each.
  • Windows/Win32 remain separate Fabric/Paper endpoints, other platforms preserve behavior, and native/package checks and necessary changesets pass.

Coordination

Restoring Accordion coverage unblocks the original focus-survival and accessibility cohorts (#4347/#4343). Coordinate #4349 for required-pipeline qualification. Native package/component fixes may also relate to #3971/#4274, but those broader issues do not currently track these exact catalog exclusions.

主要言語
TypeScript
スター
1.4k
フォーク
179
平均マージ
2日 9時間
マージ済み PR（30日）
30

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/fluentui-react-native のほかの issue

microsoft/fluentui-react-native の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。