News for hackers. Stuff that matters.

A comment on TypeScript 3.7. Parent comment

Re:TypeScript 3.7 by simlevesque on Tuesday November 05, 2019 @05:09PM (#21457291)
You won't regret it ! It helps me every day. Just be sure to not be too strict in your tsconfig.json in the beginning.

edit: I'm refering to "noImplicit*" configuration.

[ Parent | on HN ]
Re:TypeScript 3.7 by AgentME on Tuesday November 05, 2019 @05:14PM (#21457340)
>Just be sure to not be too strict in your tsconfig.json in the beginning.

Do you mean to avoid using the "strict" rule, or are you referring to other rules? My number one Typescript suggestion is to make sure you start with "strict": true in your tsconfig.json to be sure your code has nullability correctly enforced.

[ Parent | on HN ]
Re:TypeScript 3.7 by simlevesque on Tuesday November 05, 2019 @05:16PM (#21457362)
I'm talking about "noImplicitAny", "noImplicitReturns", "noImplicitThis"... they get in my way when I'm editing. When I'm about to push my code I activate them back.
[ Parent | on HN ]
Re:TypeScript 3.7 by charrondev on Tuesday November 05, 2019 @09:27PM (#21459150)
Personally I just don’t block the result of my hot dev server on the type checking.

I follow along with types in my IDE, and in a separate command.

Basically Babel for transpilation (which strips all types, correct or not), and type checking in a separate process.

[ Parent | on HN ]