-
Notifications
You must be signed in to change notification settings - Fork 887
chore(site): refactor stories and test from page components #9603
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
Conversation
BrunoQuaresma
commented
Sep 8, 2023
- Update Storybook usage to use v7 API
- Remove render tests from integration tests and move them to stories
68d7833
to
2f55e6b
Compare
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.
Seems like tons of good stuff in here! Having Chromatic compare stories will definitely be a better solution than some of these tests getting removed.
children: [ | ||
<Cond key="1" condition> | ||
The first one shows. | ||
</Cond>, | ||
<Cond key="2" condition={false}> | ||
The second one does not show. | ||
</Cond>, | ||
<Cond key="3">The default does not show.</Cond>, | ||
], |
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 liked the earlier commit where these were fragments: React will perform better with those. Does it break the ChooseOne
component or something?
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.
Nops, it is just for the storybook. I didnt find a similar API to keep it as a fragment in the new Storybook v7 API