Controls: Fix crashing when docgen extraction partially fails

[yannbf]

Closes #

What I did

Followup work for #26774, where the controls (and docs) won't crash anymore if there's a failure when extracting prop data in docgen.

The error message is also updated to be clearer and provides a link to the docgen limitations umbrella GH issue.
As a result, there will be no failure, the type will still be displayed, but in a simpler form. The error will still be displayed, but in the dev tools instead.

Before:

After:

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

1. Use react-docgen in a project.
2. Have a button like so:

type ReproType = {
  innerProperty: { [k: string]: string };
  innerProperty2: { string: string };
  innerProperty3: Record<string, string>;
};

type ButtonProps = JSX.IntrinsicElements['button'] & {
  repro1?: ReproType['innerProperty'];
  repro2?: ReproType['innerProperty2'];
  repro3?: ReproType['innerProperty3'];
};

export function Button({ ...rest }: ButtonProps) {
  return <button {...rest} />;
}

3. See it not crash

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 2fb5ed5. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

• nx affected -t check -c production --parallel=7
• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.