-
-
Notifications
You must be signed in to change notification settings - Fork 75
Help from tslint-eslint rules? #74
Comments
@gaurav21r unfortunately, there's not a lot of value to ESLint TypeScript support from looking at that project. Basically, that project will be irrelevant if we do our job correctly because the core ESLint rules will just work. :) I'm also privately working on a plugin with TypeScript-specific rules: https://github.com/nzakas/eslint-plugin-typescript. That's an area where we could definitely use help (the core ESLint team is not involved in that). |
@nzakas Thanks for your response! What is the difference between If I understood the goals of this project correctly (#13),
|
Disclaimer: I don't actually work on these projects and don't know TypeScript, so I might be misusing some terminology here 😄 @gaurav21r
So basically, the two projects work to add TypeScript to two different steps of the ESLint process-- parsing/code input, and linting rules. Basically, typescript-eslint-parser helps with your first point, and eslint-plugin-typescript will help with your second point. Make sense? |
@platinumazure Thanks a lot! Thats a great explanation! I was almost there except I thought this repo would handle both 1 & 2 points. Just to re-iterate, if I set .eslintrc to {
"extends": "airbnb",
"parser": "typescript-eslint-parser"
} My typescript code would get linted with the AirBnb rules config? |
Yes- when this project is ready, of course. :-) On Aug 30, 2016 4:22 PM, "Gaurav Ramanan" [email protected] wrote:
|
Hi there! I don't know a lot about the TS Language Services API but I am cheering for ESLint to support TS very soon! ESLint is pretty fantastic and I think we would all win if there are fewer tools covering a larger area! Besides, eslint configs are far superior to TSLint's.
This project -> https://github.com/buzinas/tslint-eslint-rules uses the reverse methodology. I was just wondering if the core team could have a look at it and get any help from it?
Sorry if this is the wrong place to post this!
The text was updated successfully, but these errors were encountered: