-
Notifications
You must be signed in to change notification settings - Fork 1k
Conversation
|
Oh cool didn't know that's so far already, thanks @sagirk :] So TLDR: "The TypeScript community intends to meet JavaScript developers where they are, and ESLint is the tool of choice for JavaScript linting. In order to avoid bifurcating the linting tool space for TypeScript, we therefore plan to deprecate TSLint and focus our efforts instead on improving ESLint’s TypeScript support" |
|
Seems like we like that config. I'd start with the required changes so we can land this soon :] |
|
Quick update on that: I'm having some conflicts between eslint and prettier plus having all the time conflicts with master which are quite tedious. So hope in couple days it'll be done :] |
|
I really would like this to be merged soon ;) Anything from your end at @LaRuaNa 🤔 |
|
Rebase to remove conflicts? |
|
ping @LaRuaNa |
|
|
@LaRuaNa I'm poking around this PR right now, great work! Is there anything I can help you with? |
|
@jonchurch It's almost done. Needs to be rebased and perhaps might require some small fixes after rebase. If you feel like it take a look :] |
|
Awesome! Since we are using jest for testing, I'd suggest adding the This takes care of linting errors about global jest variables not being defined like I tried it out locally with these items added and it looks good. |
2af1f94 to
c69d6bb
Compare
|
I rebased this branch onto master, added There's likely a way to only run the typescript rules on typescript files, but I just disabled the one rule that I thought made sense. We aren't using babel for .js files so the rule preventing the use of require isn't useful for .js files. I also changed some of the scripts, replacing the format step in scripts that used it with a lint script, since eslint is also responsible for running prettier now. |
|
@jonchurch All good :] I'm also on it and somehow I'm not really happy with the config. There are some conflicts between eslint and prettier. _ Went through all the files and tried to sort them out but doesn't seem reasonable. It would be great to have eslint's autoFix and prettier at the same time. There is also a way to do that (Link) but as mentioned conflicts between all the configs we extend from make it not easy :] So ideas&help welcome. |
|
@LaRuaNa I agree, this isn't ready yet. The config isn't quite there, and I didn't even realize we weren't running the prettier plugin for autofixing. I'll keep working on this also as I'm interested in learning more about using eslint + typescript. |
|
Done in #315 |
Hi all,
as decided in the last meeting here a experimental PR with eslint and prettier integration based on the industry standard (airbnb config). I got from couple of mates from Microsoft the info that there is a roadmap for Typescript in which they announced that "editor team will be focusing on leveraging ESLint". I think it makes sense to move official supported platforms rather than community driven ones. ( You know what I mean, don't get me wrong :] ) So I removed tslint from our config and introduced eslint. IMO It makes also sense because of all the eslint plugins like react-hooks. They're just up to date.
So, please take a look in that, try to fix couple of eslint errors and play a bit around to get a feel for the config.
Here my vscode config you might need :]
Note: Please don't open any PRs with that config and do not merge this PR yet
refs:
microsoft/TypeScript#29288
https://eslint.org/blog/2019/01/future-typescript-eslint