-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
chore: migrate to storybook 6.0.x #17007
Comments
updated |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
🎉This issue was addressed in #17033, which has now been successfully released as Handy links: |
As we are going to leverage Storybook (SB) for convergence (primarily the Composition feature) we need to migrate to SB v6.
Tasks:
in general follow migration guide
@storybook/*
deps in whole repo (NOTE: potential merge conflicts with chore: apply single version policy on storybook #16965 )What apps/packages will be affected:
apps/vr-tests
- contains storybooks that are executed against Screener for visual regressionsstoriesOf
API (TBD if we gonna go migrate toCSF
?) - no action needed for nowpackages/storybook
- our custom package that provides various fluentui related SB extensionspackages/react-examples
uses deprecated config apisconfigure(), addDecorator()
etcmain.js
.packages/fluentui
: no action needed - SB is not being usedpackages/web-components
- they are using SB 5.3. We need to opt out explicitly probably viano-hoist
as we are not owners of this package and we don't wanna break their stuff (handled by this PR)The text was updated successfully, but these errors were encountered: