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
JSCS is now end of life, and with #2 having implemented ESLint, there should be no reason to continue to include JSCS.
Removing it sooner, and bumping the major version number to indicate breaking compatibility, is likely to be far less painful than doing it later.
The text was updated successfully, but these errors were encountered:
Yes, I would agree. With ESLint in place and using the shared WP config (as in #2), it can be removed.
Sorry, something went wrong.
Closing this issue, JSCS was removed in commit 3a12406
craigsimps
No branches or pull requests
JSCS is now end of life, and with #2 having implemented ESLint, there should be no reason to continue to include JSCS.
Removing it sooner, and bumping the major version number to indicate breaking compatibility, is likely to be far less painful than doing it later.
The text was updated successfully, but these errors were encountered: