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
Due to the increasing size of the team, code quality might suffer as everyone has their coding style. To remedy this, we should implement stricter ESLInt and ts.config rules. Due to workflow in #29 , these checks will be done automatically so this will save us a lot of time in the future.
Prereq
Requires a deep knowledge of javascript and typescript.
Example
Explore if we should make this true (Currently it is false): "noImplicitAny": ???
The text was updated successfully, but these errors were encountered:
noImplicitAny should remain in use, as it helps catch issues where type inference fails. Normally when this happens (without noImplicitAny), we opt out of type checking automatically (and implicitly), which makes TypeScript less useful.
Oops, sorry I reversed it (fixed it in the issue). Yeah ideally we want to make it on as the issue previously was people wouldn't use typescript, and as they wouldn't get any errors, they assumed they were fine. But like you said, this will require fixing a lot of stuff, but in the future will fix a lot of issues
Context
Due to the increasing size of the team, code quality might suffer as everyone has their coding style. To remedy this, we should implement stricter ESLInt and ts.config rules. Due to workflow in #29 , these checks will be done automatically so this will save us a lot of time in the future.
Prereq
Example
Explore if we should make this true (Currently it is false):
"noImplicitAny": ???
The text was updated successfully, but these errors were encountered: