-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React: Use Act wrapper in Storybook for component rendering #30037
base: next
Are you sure you want to change the base?
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a52aec2. 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 targetsSent with 💌 from NxCloud. |
b4a1714
to
4c40b5f
Compare
4c40b5f
to
95e2429
Compare
95e2429
to
13e3869
Compare
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
…ENV handling in build scripts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 file(s) reviewed, 5 comment(s)
Edit PR Review Bot Settings | Greptile
let result; | ||
act(() => { | ||
result = cb(); | ||
return result; | ||
}); | ||
return result; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: result variable could be undefined if act throws an error
76e10e5
to
32b52ee
Compare
32b52ee
to
a52aec2
Compare
Closes #
What I did
Previously, we have wrapped mounting and unmounting of React component, as well as test interactions via userEvent by
act
in a portable stories environment. Now we are adapting this behaviour to configure@storybook/test
to wrap all component interactions and mounting/unmounting withact
. This will make sure, that we can actually await a components rendering properly before we continue to the next Storybook render lifecycle phase.Background:
The A11y addon has issues to find the right timing to trigger an automated test run if a component uses Suspense (e.g. RSC). With
act
we can actually properly await the complete rendering of a React component also in the Storybook preview, so that addon a11y can properly await its final rendering to trigger an a11y test run.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/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 pull request has been released as version
0.0.0-pr-30037-sha-13e3869b
. Try it out in a new sandbox by runningnpx [email protected] sandbox
or in an existing project withnpx [email protected] upgrade
.More information
0.0.0-pr-30037-sha-13e3869b
valentin/act-wrapping-of-components
13e3869b
1734009036
)To request a new release of this pull request, mention the
@storybookjs/core
team.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=30037
Greptile Summary
Based on the provided files and changes, here's a concise summary of the pull request:
Implements proper React act() wrapping for component rendering in Storybook, ensuring consistent behavior between development and testing environments.
act-compat.ts
to skip act wrapping in production buildsrenderToCanvas.tsx
to wrap both render and unmount operations in act() for proper component lifecycle handling__isPortableStory
flag in render context to control act wrapping behavior