Giovanni Gonzaga

👍 this would be very helpful

If I guess the `ifElse` signature correctly from the ramda docs, it should be something like (+ currying, ignored here): ```ts function ifElse(predicate: (a: A) => boolean, whenTrue: (a: A)...

At [buildo](https://www.buildo.io/) ([logo](https://raw.githubusercontent.com/giogonzo/ts-conf-talk/master/slides/buildo.svg)) we are using `fp-ts` in pretty much every TypeScript codebase that we have: React applications, Node services, internal CLI tools. The majority of the repositories is closed...

Since we are offtopic now: we also generate TS (io-ts) from Scala code, via [metarpheus](https://github.com/buildo/retro/blob/master/metarpheus/README.md) and [metarpheus-io-ts](https://github.com/buildo/metarpheus-io-ts). @vegansk to generate ADTs also have a look at [fp-ts-codegen](https://github.com/gcanti/fp-ts-codegen) 😉

just came across to https://github.com/juusaw/ts-to-io

> Lastly, it is the original typescript functionality. If you attach type { foo: string } to a variable, you can not add additional properties. Just pointing out that this...

One of the key design choices of `io-ts` is (I believe) mapping 1:1 with the TS type system, and this to me looks also one of the main strengths compared...

I did a POC of "excess" in `io-ts-types` here: https://github.com/gcanti/io-ts-types/pull/114 It is mostly a porting of https://github.com/gcanti/io-ts/issues/322#issuecomment-513170377, but, as requested in #378, also applies the same "excess" check in the...

~@mnn you can always apply `excess` to the components of the intersection right?~ EDIT: disregard, it obviously doesn't work: it would fail at the very first component, incorrectly

Hi @mikecann , the problem with "old" refinements is that they don't carry the information at the type level, so for instance, with your definition, the following is allowed: ```ts...