Closed eteeselink closed 7 years ago
Awesome, thanks a lot.
I'm really fond of tcomb and the related libraries
By the way, if TypeScript is your cup of tea, keep an eye on this project https://github.com/gcanti/io-ts. Basically is tcomb revamped, merged with tcomb-validation and compatible with the TypeScript type system (the TypeOf
operator, which allows for extracting static types from runtime types, is pretty interesting IMO).
Typescript is indeed my cup of tea, and I saw your tweet about io-ts. Now that we're going off-topic anyway, I was wondering: what's your motivation for moving from flow to ts? Our typescript code is simply typescript because we had Windows devs and Flow didn't work on Windows at the time - so no real fundamental reason. But you've invested a lot of time in Flow and now went to TypeScript, why's that? :-)
By the way, I like the idea of io-ts. Do you consider it the spiritual successor to tcomb? I'm only sad that I can't use typescript class or interface syntax with it, but I understand that that's simply a limitation to TS - without an additional generator.
I'm confused about your use case for io-ts, though. What's the point of runtime type checking inside a 100% typescript project? Relatively little, I assume, so I guess it's for safety at the border of a mixed JS-TS project, or for library APIs and the likes. Right? If I guessed right, maybe adding the use case near the top of the README might help people understand it - I only understood it now, the second time I looked at it.
@eteeselink opened an issue here https://github.com/gcanti/io-ts/issues/18 for discussing
As discussed in #362. What do you think?
BTW thanks a lot for all your fantastic open source work! I'm really fond of tcomb and the related libraries.