News for hackers. Stuff that matters.

A comment on TypeScript at Google. Parent comment

Re:TypeScript at Google by acemarke on Sunday September 02, 2018 @11:06AM (#17897224)
We're actually looking at removing the type definitions from the Redux core and punting them over to DefinitelyTyped, because neither of us primary maintainers use TS ourselves and we don't have the experience to maintain the type definitions.

Also, the CRA-TS fork runs, but the one time I played with it was when I tried to help another team set up their project, and that's when I found out it has _ridiculously_ restrictive default linting rules. Every lint error is a compile error, and it flags things like using arrow functions in render methods, which is absurd (see discussion at https://github.com/wmonk/create-react-app-typescript/issues/... ).

[ Parent | on HN ]
Re:TypeScript at Google by joshtynjala on Sunday September 02, 2018 @06:14PM (#17898975)
The first thing I do in a new CRA-TS project is make the tslint.json rules default to warnings instead. Or just disable them completely. After that, it's great! I'm actually surprised that they still haven't loosened the rules after Dan called it out a month or two ago. Seems like an easy enough fix to at least make them warnings until they choose better defaults.
[ Parent | on HN ]
Re:TypeScript at Google by Vinnl on Sunday September 02, 2018 @04:31PM (#17898496)
Haha right, it's still the case that the type definitions for Redux are very much usable though :)
[ Parent | on HN ]