-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add docs on using type information in rules #63
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
Comments
type check is available from parser service, and its same one as used in TSLint (typescript), there is additional task to do before using it, you have to get ts node from context.parserServices.esTreeNodeToTSNodeMap.get(node) will return node witch you can pass to estree has some additional nodes, and about ast structure, you can find "estimate" of structure definition for currently used version here |
@JoshuaKGoldberg once the PR lighting this up in |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
* fix(eslint-plugin) replace interface-name-prefix * fix(eslint-plugin) fix lint errors * fix(eslint-plugin) replace interface-name-prefix - fix regexp in replacement rule - move rule to upper file Co-authored-by: SuperOleg39 <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Spinning off of bradzacher/eslint-plugin-typescript#276 and as a backing documentation request to help with #62: would you mind writing some docs on how to use TypeScript-specific features (the type checker? anything else?) on top of ESLint?
The text was updated successfully, but these errors were encountered: