-
Notifications
You must be signed in to change notification settings - Fork 55
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(ARCH-662): upgrade storybook to 7 #4538
Conversation
…i into jmfrancois/chore/storybook-beta
Co-authored-by: Inna Ivashchuk <[email protected]>
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.
Need to add those deps in storybook-docs
figma-js
react
classnames
import { useState, useEffect } from 'react'; | ||
import type { ChangeEvent, FormEvent } from 'react'; | ||
import { IconGallery, IconItem } from '@storybook/blocks'; |
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.
Import are not used
@@ -0,0 +1,9 @@ | |||
import statuses from './status.json'; | |||
import { Statuses, ComponentStatuses } from '@talend/storybook-docs'; |
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.
@talend/storybook-docs should be added as dependency
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.
I will use a joker here to fix that in a later PR.
We must remove the DS from all our docs blocks and just use plain react or svg things.
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.
Need to add those deps in storybook-docs
figma-js
react
classnames
…i into jmfrancois/chore/storybook-beta
What is the problem this PR is trying to solve?
We have a bunch of force resolution because of storybook dep on webpack 4
Fall under unset-value security issue.
What is the chosen solution to this problem?
DEMO: http://4538.talend.surge.sh/
details:
Will be done in a next PR
Here is the common storybook hierarchy
Please check if the PR fulfills these requirements
yarn changeset
to a request a release from the CI if wanted.[ ] This PR introduces a breaking change