-
Notifications
You must be signed in to change notification settings - Fork 179
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 ESLint config #1068
Update ESLint config #1068
Conversation
- Use ESLint’s recommend ruleset - Make config more explicit - Do not blindly use wordpress/recommended ESLint ruleset. Makes it easier to extract / split out later.
Size Change: -63 B (0%) Total Size: 871 kB
ℹ️ View Unchanged
|
assets/src/edit-story/components/colorPicker/test/useColor/removeCurrentStop.js
Show resolved
Hide resolved
@@ -47,6 +47,7 @@ function EditElement({ element }) { | |||
actions: { getBox }, | |||
} = useUnits(); | |||
|
|||
//eslint-disable-next-line @wordpress/no-unused-vars-before-return |
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'm wondering why doesn't it know about the usage? Does it not expand JSX before running these rules?
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.
WordPress/gutenberg#21358 has a pending fix with details.
@wordpress/eslint-plugin/recommended
ESLint ruleset. Makes it easier to extract / split out later.@wordpress/eslint-plugin
@wordpress/eslint-plugin/i18n
ruleset and fix issues