(Replying to PARENT post)

I was a Flow holdout for the longest time. TypeScript's support for discriminated unions is one of the things which finally won me over. Super glad to see it being improved upon here.
๐Ÿ‘คbluepnume๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

Flow also supports "discriminated unions" [0], and did so before TypeScript (Flow's announcement in July 2015: https://flow.org/blog/2015/07/03/Disjoint-Unions/, TypeScript's announcement in August 2016: https://devblogs.microsoft.com/typescript/announcing-typescr...), though it doesn't yet support destructuring the "kind" field as was just added to TypeScript.

[0] https://flow.org/try/#0C4TwDgpgBAggxsAlgewHZQLwCgq6gHygG8oBr...

๐Ÿ‘คGeZe๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

As somebody who never worked with Flow but loves TS, what does Flow offer that the latter canโ€™t do?
๐Ÿ‘คgherkinnn๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

Flow feels pretty dead. The VSCode extension is broken in major ways and hasnโ€™t gotten a major update in years. The only mainstream editor that fully supports it is IntelliJ.
๐Ÿ‘คsymlinkk๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0