-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add eslint settings for TypeScript #1205
Conversation
Nice. Good start being able to lint the TypeScript separately. 👍 I tried turning it on for editor too by combining in I see there is https://github.com/standard/eslint-config-standard-with-typescript which could be appropriate since we are using I suggest if we keep two config files then use same filetype for |
2036ceb
to
8c666fe
Compare
Modified to use 'standard-with-typescript'. I prefer setting with As you mentioned, the file type is different from |
Let's go with |
I suggest add one rule to restore this to default and avoid a lot of errors. We have our own "semi" rule for javascript, so reasonable we need one for TypeScript too. Feel free to make layout a bit more compact, I used fully expanded layout here.
As otherwise get errors for the semicolons in this:
|
Might be able to get the linting working with single configuration file using |
2ca3a31
to
a64398e
Compare
Thank you for the review! I have modified it based on your feedback. |
I can now see the errors in VisualStudio Code too when I open the TS files, nice! Quite a few things to fix after this lands, but mostly easy. 😅 Could lint both the typescript files:, script:
|
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.
LGTM
👍 Nice changes to bring our TypeScript style support up to level of our JavaScript for future work with a lint script and editor support. |
Thanks for the review! |
Pull Request
Problem
#1191 (comment)
Solution
I tried setting TypeScript as a trial.
(@shadowspawn Close it if you are already working on it.)
ChangeLog