-
-
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. |
* giteaofficial/main: Remove padding override on `.ui .sha.label` (go-gitea#35864) fix(api/repo/contents): set the dates to now when not specified by the caller (go-gitea#35861) Remove `fix` Make targets (go-gitea#35868) Refactor ls-tree and git path related problems (go-gitea#35858) Fix pull description code label background (go-gitea#35865) Make ACME email optional (go-gitea#35849) Remove wrong code (go-gitea#35846) Fix Arch repo pacman.conf snippet (go-gitea#35825) Port away from `flake-utils` (go-gitea#35675) Update golangci-lint to v2.6.0 (go-gitea#35801) Add a doctor command to fix inconsistent run status (go-gitea#35840) Fix viewed files number is not right if not all files loaded (go-gitea#35821) Fix incorrect pull request counter (go-gitea#35819) Fix a number of `strictNullChecks`-related issues (go-gitea#35795) ignore .worktrees as a "special folder" (go-gitea#35835) upgrade go mail to 0.7.2 and fix the bug (go-gitea#35833)
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.