EllAchE
EllAchE
I'm looking to implement a Zod schema that supports "hard" and "soft" type definitions in the same schema with little boilerplate. What I mean by that is combining the behaviors...
Adds features: - Recursive flag for finding .vcf files - Support mobile phone - Support address - Support Birthday - Separate first/last name in output file - Print unknown keys...
[luluNextData.txt](https://github.com/colinhacks/zod/files/15241501/luluNextData.txt) When emitting declaration files for a complex nested json the resulting declaration file can end up being quite large. I've shared a schema above generated from a large json...
There are limitations to the currenty json-to-zod and json-to-ts libraries in use. I raised one specific issue in https://github.com/ritz078/transform/issues/401, but others include using any over union types, using null where...
Having nullable properties in a json array results in excessively large zod schemas. I encountered this specifically when converting JSON to zod but it applies in other use cases as...
I'd like to suggest adding a "merge" option to the default diff methods to make diffs more readable/useful. Here's a diffWords & diffChars example visualizing current behavior vs my proposed...