-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
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
Made ESLint lint all TypeScript files and fix a few linter errors #273
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry, we must include the preact
imports in preact code or the compilation will fail. Eslint doesn't know that it's needed.
There is possibly a linter rule exemltion we need to import for this, I've not checked
…kshot into j94/unused-imports
"no-unused-vars": "off", | ||
"@typescript-eslint/no-unused-vars": ["error"], | ||
"no-useless-constructor": "off", | ||
"@typescript-eslint/no-useless-constructor": ["error"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't figure out why the regular eslint rules were still being used.
Only the TypeScript variants make sense for this code base.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, suppose we can come back to this one when it poses a problem for us. The linter seems happy for the moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks a ton for cleaning up the .eslintrc.js file :)
"no-unused-vars": "off", | ||
"@typescript-eslint/no-unused-vars": ["error"], | ||
"no-useless-constructor": "off", | ||
"@typescript-eslint/no-useless-constructor": ["error"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, suppose we can come back to this one when it poses a problem for us. The linter seems happy for the moment.
package.json
. Currently,*.ts
files directly in thesrc
folder are not linted on all operating systems because**
resolves to folder names.test
andweb
folder with slightly adapted rules.