-
Notifications
You must be signed in to change notification settings - Fork 804
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
eslint: Enable react/no-unknown-property
rule
#39414
Conversation
For the most part the fixes needed here switch to corresponding React properties rather than properties that get passed-through without React validation, e.g. `class`→`className`, `stroke-width`→`strokeWidth`, and `itemprop`→`itemProp`. In one place we ignore the rule warning about `transform-origin`, which needs to be a pass-through until React 19 adds `transformOrigin`. And in one place we remove the IE8(!) `allowTransparency` property that React removed in 2017.
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
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. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
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.
The E2E failure doesn't seem to be related to the changes.
For the most part the fixes needed here switch to corresponding React properties rather than properties that get passed-through without React validation, e.g. `class`→`className`, `stroke-width`→`strokeWidth`, and `itemprop`→`itemProp`. In one place we ignore the rule warning about `transform-origin`, which needs to be a pass-through until React 19 adds `transformOrigin`. And in one place we remove the IE8(!) `allowTransparency` property that React removed in 2017.
Proposed changes:
For the most part the fixes needed here switch to corresponding React properties rather than properties that get passed-through without React validation, e.g.
class
→className
,stroke-width
→strokeWidth
, anditemprop
→itemProp
.In one place we ignore the rule warning about
transform-origin
, which needs to be a pass-through until React 19 addstransformOrigin
. And in one place we remove the IE8(!)allowTransparency
property that React removed in 2017.Other information:
Jetpack product discussion
Followup to #38436
Does this pull request change what data or activity we track or use?
No
Testing instructions: