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
From my experience, it's better to have two different configs: one for development and one for CI/prod. For example, noImplicitAny can improve type coverage, but it is tough to program with it enabled. Similarly, allowUnreachableCode prevents dead code, but it is also inconvenient during rapid prototyping.
Go through use of any and introduce better types where appropriate (I have a few in mind)
The text was updated successfully, but these errors were encountered:
As of 23 Jun:
Old list for reference:
Known bugs:
Since Convert BCD to TypeScript #16593 was merged, BCD script
ts-node test/lint
fails on NodeJS 16Demo: CI run on NodeJS 16
This bug was identified by @queengooborg in Convert BCD to TypeScript #16593:
Solutions:
node_modules
while we wait forts-node
to accept the fix. There are multiple ways to do it. Use my patched version of ts-node #16669TS declarations, data schema, and JSDoc comments can go out of sync
Solutions:
Future improvements:
noImplicitAny
can improve type coverage, but it is tough to program with it enabled. Similarly,allowUnreachableCode
prevents dead code, but it is also inconvenient during rapid prototyping.any
and introduce better types where appropriate (I have a few in mind)The text was updated successfully, but these errors were encountered: