3 ms·
Zod is quite unpleasant to use, IME, an has some edge cases where you lose code comments. From experience, we end up with a mix of both Zod and types and somet
by CharlieDigital 11mo ago
Zod is quite unpleasant to use, IME, an has some edge cases where you lose code comments.
From experience, we end up with a mix of both Zod and types and sometimes types that need to be converted to Zod. It's all quite verbose and janky.
I quite like the approach of Typia (uses build-time inline of JavaScript), but it's not compatible with all build chains and questions abound on its viability post Go refactor.
- hermanradtke 11mo ago> we end up with a mix of both Zod and types and sometimes types that need to be converted to Zod In my code, everything is a Zod schema and we infer interfaces or types from the schemas. Is there a place where this breaks down?
- CharlieDigital 11mo agoNot that I know of aside from code comments (which I like), but I much prefer writing TypeScript to Zod