You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
@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: