Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Infrastructure: Restore Storybook stories excluded by native desktop crashes

未关闭
  • 哪里不对？
#4,344 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时
30 天内合并 PR
30

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/fluentui-react-native 的其他 Issue

查看 microsoft/fluentui-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。