-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Notice: Remove knobs in stories #46956
Conversation
Size Change: 0 B Total Size: 1.32 MB ℹ️ View Unchanged
|
Flaky tests detected in 0c58bbd. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/3859399643
|
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.
LGTM 🚀
// TODO: Add a story involving NoticeList to help people understand | ||
// the difference between onDismiss/onRemove. |
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.
Similar situation to Snackbar
and SnackbarList
. In those situations, should we treat these components as part of the same family? In that case, which component is the "main" component?
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 think we'd need to evaluate each case based on whether the Foo
component can be used independently of the FooList
or FooGroup
. If it can be used independently, that would be the main component.
Part of #35665
What?
Remove the Knobs add-on from
Notice
stories.Why?
This is now a blocker for supporting npm 8 (#46443).
How?
Just a quick, minimal refactor.
Testing Instructions
npm run storybook:dev
Notice
component.