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
It'd enable strictNullChecks everywhere and temporarily ignore all existing errors. However this means we'll have 1.9k lines of // @ts-expect-error temporarily cluttering our code. We have just about 130k lines now (95k of pure code) so it wouldn't be overwhelming.
Demo:
47cbf3a
Pros:
new code will hopefully be stricter
Cons:
@ts-expect-error silences all errors on those lines
Given the current amount of non-strict code (1900 LoC), enabling strictNullChecks feels impossible at this point. My previous attempt is probably still the solution with the best DX to enable it on new files without completely silencing the existing files:
Long-term code quality initiative, incremental plan to turn on TypeScript's
strictNullChecks
optionReference on incremental migration:
The text was updated successfully, but these errors were encountered: