refactor: migrate templates from using tslint to eslint #1467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #1467 +/- ##
=========================================
- Coverage 75.16% 75.07% -0.1%
=========================================
Files 73 73
Lines 2130 2130
Branches 397 397
=========================================
- Hits 1601 1599 -2
- Misses 407 409 +2
Partials 122 122
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summarize your changes:
Last year, it was declared that
tslintwas going to be deprecated in favor ofeslint: https://eslint.org/blog/2019/01/future-typescript-eslintAs of tslint v6.0.0, it has been marked as deprecated: https://www.npmjs.com/package/tslint/v/6.0.0
This PR updates the templates to use the recommended linter,
eslint.