-
Notifications
You must be signed in to change notification settings - Fork 22
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 TypeScript type-checking to all rules #241
Comments
I'm on board in principle, but I would want to make sure the developer burden is not significantly increased. I skimmed the PR but need to look through it more thoroughly. |
@bmish Finally coming back to this... I'm open to this but I have one question. How do we ensure that type info (in doc comments) is added for new code/types? And are there ways to auto-generate at least some of those so the dev experience isn't too annoying? |
We don't need to convert our JavaScript files to TypeScript, but by adding JSDoc comments with types and using the TypeScript checkJs option, we can get the benefits of type-checking. See this PR for an example and list of benefits: square/eslint-plugin-square#723.
The text was updated successfully, but these errors were encountered: