We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We now have jshint and eslint to take care of code style standards. We should replace jshint with eslint.
If the current set of Jshint rules is inherited from core, there's a migration ruleset in @wordpress/eslint-plugin that we can use directly.
@wordpress/eslint-plugin
I see some differences between Jetpack and WordPress jshint files — could be that Jetpack one is just out of date?
There are some jshint inline rules that had been removed from JShint long time ago already:
jetpack/modules/after-the-deadline/atd-nonvis-editor-plugin.js
Line 1 in 201ec52
PR in Gutenberg for reference WordPress/gutenberg#12840
cc @brbrr
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
We now have jshint and eslint to take care of code style standards. We should replace jshint with eslint.
If the current set of Jshint rules is inherited from core, there's a migration ruleset in
@wordpress/eslint-plugin
that we can use directly.I see some differences between Jetpack and WordPress jshint files — could be that Jetpack one is just out of date?
There are some jshint inline rules that had been removed from JShint long time ago already:
jetpack/modules/after-the-deadline/atd-nonvis-editor-plugin.js
Line 1 in 201ec52
PR in Gutenberg for reference WordPress/gutenberg#12840
cc @brbrr
The text was updated successfully, but these errors were encountered: