Alexey Orlenko

On a side note, I was recently thinking about OCaml-style `type T` exports in each module to be nice to have: ```ts import * as Option from 'fp-ts/lib/Option'; function f(x:...

@christianbradley turns out there's already an even better solution than what I suggested earlier in this thread. See this: https://github.com/gcanti/fp-ts/issues/1185#issuecomment-613334914

Hidden as the comments this was about are now deleted Hey, let's keep the conversation civil and on track, because it becomes kinda heated. @gcanti what do you think about...

@steida: what @SRachamim proposes is indeed a little bit more ergonomic than the current status quo outlined in the comment that you linked too, IMO. Consider that you won't need...

The current design is primarily oriented at using string literals in a type-safe way, and changing this to regular enums would be a significant breaking change for many if not...

@SevInf can this issue be closed now or is there anything else that needs to be done besides https://github.com/prisma/prisma/pull/13455?

> I'll let @aqrln review, note from the past We mentioned in https://github.com/prisma/prisma/pull/13823 that We want to upgrade directly to 5.x later., I'm not sure why. Maybe it's fine to...

> I'd rather try type casting with [email protected], as the problem of it is only about typing The problem is we're re-exporting the template tag from that library. We could...

Overwriting the files inside the package is quite problematic, otherwise we could just generate the client inside `@prisma/client`. I guess in this case it might be relatively okay with popular...

> Webstorm Build #WS-221.5080.193 I was wondering, in fact, if you might be using IntelliJ IDEA or WebStorm with their static analysis engine instead of the language server (or perhaps...