-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Fix a number of strictNullChecks-related issues
#35795
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
Conversation
This reverts commit bd95b69.
|
Regarding this |
|
Found a better way, Edit: as per this, the resulting type was not correct, so I used the longer form. |
Signed-off-by: silverwind <[email protected]>
Signed-off-by: silverwind <[email protected]>
|
Diff is now minimal, I reverted a few unnecessary things. |
In preparation to work on enabling https://www.typescriptlang.org/tsconfig/#strictNullChecks, I fixed all the issues outside of
web_srcthat came up when the option was enabled. There was also one lint issue in web_src that apparently only came up with the option enabled, so I fixed that as well.isTruthyis introduced because Typescript has a bug regardingfilter(Boolean)which they are seemingly unwilling to fix.