-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Core: Introduce run over play in portable stories, and revert back play changes of 8.2 #28764
Conversation
…ay-to-run' into kasper/introduce-run
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 2772623. 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 1 targetSent with 💌 from NxCloud. |
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.
11 file(s) reviewed, 30 comment(s)
Edit PR Review Bot Settings
@@ -44,7 +44,8 @@ export type ComposedStoryFn< | |||
> = PartialArgsStoryFn<TRenderer, TArgs> & { | |||
args: TArgs; | |||
id: StoryId; | |||
play: (context?: Partial<StoryContext<TRenderer, Partial<TArgs>>>) => Promise<void>; | |||
play?: (context?: Partial<StoryContext<TRenderer, Partial<TArgs>>>) => Promise<void>; |
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.
style: Making play
optional might cause issues if existing code relies on it being present.
test-storybooks/portable-stories-kitchen-sink/react/stories/Button.test.tsx
Show resolved
Hide resolved
@@ -117,6 +117,6 @@ it('should pass with decorators that need addons channel', () => { | |||
// Batch snapshot testing | |||
const testCases = Object.values(composeStories(stories)).map((Story) => [Story.storyName, Story]); | |||
it.each(testCases)('Renders %s story', async (_storyName, Story) => { | |||
await Story.play(); | |||
await Story.run(); |
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: Verify that the run
function maintains the same performance characteristics as play
.
test-storybooks/portable-stories-kitchen-sink/svelte/stories/Button.test.ts
Show resolved
Hide resolved
test-storybooks/portable-stories-kitchen-sink/svelte/stories/Button.test.ts
Show resolved
Hide resolved
test-storybooks/portable-stories-kitchen-sink/svelte/stories/Button.test.ts
Show resolved
Hide resolved
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Core: Introduce run over play in portable stories, and revert back play changes of 8.2 (cherry picked from commit 3b65e72)
What I did
We overloaded the
play
function in 8.2, so that it could be used to run the whole story whentestingLibraryRender
is set.However, we found out that this design is hard to understand and doesn't work when you want to reuse a play function of one story in another story. Especially when we would move to CSF4 where every story will be portable by default.
Therefore we are introducing a new method of
composeStories
calledrun
. Which is not overloaded, and will always run the whole story, includingloaders
,beforeEach
,mount
andplay
.We are reverting that change. If you are already started using
testingLibraryRender
in combination withplay
it means that you need to move from using.play
to.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/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>