-
Notifications
You must be signed in to change notification settings - Fork 800
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
Button Component: update to use non-deprecated attributes #23242
Conversation
This should warnings such as: ``` Button isDefault prop is deprecated since version 5.4 and will be removed in version 6.2. Please use variant="secondary" instead. ```
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
Backup plugin:
|
This should get us rid of warnings such as: ``` Warning: React does not recognize the `isLarge` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `islarge` instead. If you accidentally passed it from a parent component, remove it from the DOM element. ```
We use variant instead, since WordPress/gutenberg#31713
This was already refactored in #19778, but didn't need to remain that complicated.
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!
Pushed a rebased version. My Jetpack's product-detail-card was conflicting |
Great news! One last step: head over to your WordPress.com diff, D76075-code, and commit it. Thank you! |
r241235-wpcom |
Changes proposed in this Pull Request:
The
Button
component has changed a bit in the past few years, for example in WordPress/gutenberg#31713 Let's update all parts of Jetpack accordingly, this should avoid warnings such as:Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
Block editor
You can repeat the same steps with other elements touched by this PR. All in all it should be a fairly straightforward change imo.