Switch from TSLint to ESLint (typescript-eslint) #6
Conversation
This file contains 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
some others, with a TODO in some cases.
|
@goblindegook Any update on this? TypeScript are moving to ESLint so it would be good to migrate this Gatsby starter over too. |
|
Just migrated to ESLint, changing some other code along the way. Thanks for the help on this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I removed what I believe are all traces of TSLint. I put in what seems to be a good .eslintrc.js for typescript-eslint. Since a bunch of files then complained (e.g. type -> interface), I made some changes and put in some comments to suppress warnings.