This repository was archived by the owner on Apr 12, 2024. It is now read-only.
chore(*): switch from JSHint/JSCS to ESLint #14993
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
A build-related refactor.
What is the current behavior? (You can also link to an open issue here)
Code is linted via JSHint+JSCS.
What is the new behavior (if this is a feature change)?
Code is linted via ESLint.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements
Tests for the changes have been added (for bug fixes / features)Docs have been added / updated (for bug fixes / features)Other information:
This is the last commit of PR #14952 backported to the
v1.5.x
branch with some required changes and.catch -> ['catch']
,.finally -> ['finally']
. The other commits from that PR are already backported; they weren't dangerous and cherry-picked cleanly.This needs to be reviewed with two things in mind: the PR shouldn't introduce security issues and backwards incompatible changes.