Dmitry Zakharov
Dmitry Zakharov
In `rescript-schema`, I solved it by publishing the package with `.gen.ts` files, containing the core types. There's no need to include types for functions.
Should fix the TS infer logic. Thanks 🫡
Fixed in the commit https://github.com/DZakh/rescript-schema/pull/109/commits/9d1e579a7ad5f6aeaefae050c3cd84d18acf50ad
1. Yeah, the reasoning behind it was that it's convenient in ReScript, but I agree with you that for TS it's better to keep the type as it is. I'm...
I'll keep the current API and stop transforming null to undefined.
Hm, I see only `Failed parsing at root. Reason: Expected {}, received 1` in runtime. I don't really understand what you mean by 7 blocks of error. But in this...
But I'll think about how to prevent the case of forgetting to use `s.field` inside of `S.object` 🫡
Wow, Bun looks completely broken 😱 I don't know how to fix it, but I'll try. Also, I plan to make the schema object cleaner in the V10, so `expected`...
Thanks for letting me know 🫡
Message is a getter here https://github.com/DZakh/rescript-schema/blob/92f8e75d3e3003054c30e422da750fdc3b0abbe1/src/S_Core.res#L401-L403