-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update Button prop name type to variant #18774
Update Button prop name type to variant #18774
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
I have read the CLA Document and I hereby sign the CLA |
@georgewrmarshall I am done with all requested changes, please can you or someone else review this PR? |
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 🚀
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.
Hey @hakeemullahjan, these changes look great! One small detail is that the BUTTON_VARIANT
should be singular without the S
? Could you please update accordingly?
Yeah sure, No problem. |
I have double-checked all the files which are using the |
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! Thanks for your contribution 🙏
Explanation
In this PR, I worked on issue #18693, I had to replace the prop value from
type
tovariant
to make it more consistent with other componentsui/components/component-library
and luckily this issue was assigned to me.All files under this directory
ui/components/component-library/..
have been changed. Following changes are:type
tovariant
BUTTON_TYPES
toBUTTON_VARIANTS
ui/components/component-library/button/button.constants.js
ui/components/component-library/button/button.js
ui/components/component-library/button/button.stories.js
ui/components/component-library/button/button.test.js
ui/components/component-library/button/index.js
ui/components/component-library/button/README.mdx
ui/components/component-library/index.js
ui/components/app/modals/hold-to-reveal-modal/hold-to-reveal-modal.js
ui/components/app/terms-of-use-popup/terms-of-use-popup.js
ui/components/institutional/compliance-settings/compliance-settings.js
ui/components/multichain/network-list-menu/network-list-menu.js
ui/pages/create-account/connect-hardware/index.js
ui/pages/institutional/confirm-add-custodian-token/confirm-add-custodian-token.js
ui/pages/institutional/confirm-add-institutional-feature/confirm-add-institutional-feature.js
ui/pages/keychains/reveal-seed.js
ui/components/app/snaps/snap-version/snap-version.js
ui/components/institutional/custody-confirm-link-modal/custody-confirm-link-modal.js
ui/pages/settings/snaps/view-snap/view-snap.js
Screenshots/Screencaps
[README] Button
Before
After
[Storybook] Components / ComponentsLibray / Button - Default
Before
After
[Storybook] Components / ComponentsLibray / Button - Type to Variant
Before
After
[Storybook] ui/components/app/terms-of-use-popup/terms-of-use-popup.js
Before
After
[Storybook] ui/components/institutional/compliance-settings/compliance-settings.js
Before
After
[Storybook] ui/components/multichain/network-list-menu/network-list-menu.js
Before
After
[Storybook] ui/pages/create-account/connect-hardware/index.js
Before
After
[Storybook] ui/pages/institutional/confirm-add-custodian-token/confirm-add-custodian-token.js
Before
After
[Storybook] ui/pages/institutional/confirm-add-institutional-feature/confirm-add-institutional-feature.js
Before
After
[Storybook] ui/pages/keychains/reveal-seed.js
Before
After
Manual Testing Steps
yarn storybook
then open http://localhost:6006/ and start comparing above changed components with https://metamask.github.io/metamask-storybook/?path=/story/components-componentlibrary-button--default-storyPre-merge author checklist
Pre-merge reviewer checklist
If further QA is required (e.g. new feature, complex testing steps, large refactor), add the
Extension QA Board
label.In this case, a QA Engineer approval will be be required.