With TS 4.1 does [1, 2, undefined, 4].filter(element => element !== undefined) infer the correct return type of ‘number’ now? Instead of the incorrect return type ‘number | undefined?’ That would be a real productivity boost for me!


What's the difference between these two ways of transforming a string type that are shown in the blog post? The former doesn't actually work in the playground

chuckletmilk's tweet image. What's the difference between these two ways of transforming a string type that are shown in the blog post? The former doesn't actually work in the playground
chuckletmilk's tweet image. What's the difference between these two ways of transforming a string type that are shown in the blog post? The former doesn't actually work in the playground

Template literal types are an amazing feature and I am excited that you pursued them given that many established JS APIs will now be able to be typed. On the other hand God help the souls who have to navigate through some of the horrifying types some people will create.


Great changes overall, I'm only concerned about "Conditional Spreads Create Optional Properties". Arguing that "some people have hundreds of optional spreads in a single object" doesn't seem valid to me, because if you are in that situation, you are probably doing something wrong


Great job @typescript team!!! I'd love some reviews and support on this PR github.com/i18next/react-…, which makes i18n fully type-safe using the new features from Typescript 4.1!


@drosenwasser I think there is a mistake in the first person.on("frstNameChanged") example where the second example is mistakenly marked as error.


Template Literal Types sound weird TBH, it feels like runtime stuff


United States Trends
Loading...

Something went wrong.


Something went wrong.