-
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
Storybook: Support dashicons for testing #43721
Conversation
Size Change: 0 B Total Size: 1.24 MB ℹ️ View Unchanged
|
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 also tried launching StoryBook locally and confirmed that it works as expected 👍
Thank you!
0431c40
to
a7f218d
Compare
Interesting PR! Some time ago I worked on removing all dashicon usages from Storybook, since dashicons are apparently "unofficially deprecated" (as Riad mentioned). The idea behind that PR is that we could start the deprecation by stopping to use I see that @mirka also opened #43725, so I wonder — what is the short term plan, and the long term plan? Is it a good idea to add |
It's still questionable whether we can actually deprecate dashicons, and since we are getting active bug reports (#43574) related to their use, I think we need to be supporting (i.e. testing) them in the meantime. In any case I think we should start by updating our docs, even if we can't formally deprecate. A number of them (e.g. Icon, DropdownMenu) still prominently mention dashicons. gutenberg/packages/components/src/dropdown-menu/README.md Lines 135 to 137 in b4417e9
|
Sounds good |
Closes #43700
What?
Adds the dashicons stylesheet to the "WordPress" preset in the Global CSS Injector.
Why?
Some components need to support dashicons for backward compatibility. We should be able to test that in Storybook.
Testing Instructions
npm run storybook:dev
Screen Recording
CleanShot.2022-08-31.at.03.33.08.mp4