Fix ESLint config & boilerplate files #20
Merged
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
New stricter TS ESLint rules caused a *lot* of errors, due to implicit `any` use. Also the ESLint config is now separated between .js and .ts files, so the TS rules only apply to .ts files. The new rules also caused a lot of unfixable errors when applied to .js files.
|
👍 |
Merged
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.
New stricter TS ESLint rules caused a lot of errors, due to implicit
anyuse. Also the ESLint config is now separated between .js and .ts files, so the TS rules only apply to .ts files. The new rules also caused a lot of unfixable errors when applied to .js files.