-
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
Improve Button
matrix in visual regression test
#64120
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: 0 B Total Size: 1.76 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.
🚀
love this!
Follow-up to #62480 (comment)
What?
Convert the Button variant matrix into a more easily viewable table, and add the following missing prop combinations:
isBusy
isDestructive
isPressed
Why?
Adding these prop combinations helped catch potential regressions in #62480.
Also, it was getting harder to understand which button was what, so it needed some better labeling.
Testing Instructions
npm run storybook:e2e:dev
and see the Button ▸ Variant States story.See readme if you need more detail.
Screenshots or screencast