-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Typescript Strict mode #611
Comments
I was wondering about this because linter errors often come up when editing. Is this really an important, realistic goal? There are 1,763 errors from |
That's been taken care of. Thats the current behavior. The goal is to ensure PRs get rejected if linting falls. And we need to fix all errors,. |
|
I might be confused, I'm referring to output of |
To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves. |
The text was updated successfully, but these errors were encountered: