New: parseForESLint method and parser services

[JamesHenry]

Here is the source for the restrict-plus-operands rule I was able to create in eslint-plugin-typescript when using this feature branch and the branch from this ESLint PR eslint/eslint#6975:

It will be very hard to predict / hard to maintain exactly which TypeScript helpers will be useful in plugins rules, so for now I have exposed the full TypeScript API via ts.

[nzakas]

I'm just holding off on reviewing until I land the corresponding functionality in ESLint, just in case something changes.

[JamesHenry]

eslint/eslint#6975 was merged so this should now be ready for review :)

[nzakas]

Let's make sure we've thought this interface through completely. Are you sure about all of these?

Is ts the right name to expose? (Will people know what it is?)

Is "program" the correct name? Or should it be "TSProgram" (can't remember if that's a node or something else)

In any case, it seems like this interface should be documented in the README.

[JamesHenry]

Thanks, @nzakas! I'll loop back round to this once TS 2 support is complete :)

[JamesHenry]

Closing for now, as there is no direct action item off the back of it, and there are more pressing tasks.

Will pick this up again soon when building out more complex rules in the plugin

[j-f1]

I’d like to see this feature happen — I’m writing a custom rule that uses type information, and this would make that rule possible much more useful. (xref desktop/desktop#3550)

[JamesHenry]

We've been working on improved parser integrations in general in ESLint: eslint/eslint#8755

This will land soon and then we can start building things out on the typescript-eslint-parser side