Enable Typescript "strict" mode across the repo #792
Labels
Priority: Medium
Something that should be tried to be done in this release, but not as important as High priority.
Size: Large
Something that may take a week up to a month to implement.
Type: Dev/Internal
Something that is more internal to development than end user facing.
Type: Enhancement
Something that builds on top of what already exists
When we started the rewrite we didn't enable
"strict": true
in our tsconfigs, which was a mistake. It provides much stronger type-checking, especially for forcing you to handling possibleundefined
andnull
s better.I had a quick go and switching over when doing the Nx migration but found
class-validator
too annoying and forgot about it. Sikari in Discord recommends these settingsLet's aim to get
"strict": true
in our roottsconfig.json
and any projects that really need it disabled (maybe backend E2E tests) can override in their own tsconfig. If we can do E2E tests as well then great, but doesn't matter at all as much. Most of our libraries are using strict mode already, but frontend and backend apps have it off:The text was updated successfully, but these errors were encountered: