21–30 of 77 posts
Possibly stupid question, but why does the dog array validate: const dogsList = z.array(dogSchema); dogSchema.parse([ { name: 'Cujo', neutered: null }, { name: 'Fido', age: 4, neutered: true }, ]); // passes Since 'Cujo' doesn't have an age? Assuming it's the same dogSchema as in the previous block, age is required, right? Oh, and a minor typo: This lets you confidently This way you can confidently... .
Also fixed the other typo :)
Thanks!!
No mention of runtypes which looks pretty similar? https://github.com/pelotom/runtypes
No support for recursive types (which I personally want/need for my project).
I really like their API for constraint checking...might have to steal that...
[UPDATE] runtypes actualyl does support recursive types! My bad! Great lib.
https://github.com/tetranoir/presi
A main difference is I tried to get rid of having a separate line to create the Type and I tried to get rid of having to learn a new libary's api as much as possible.
Earlier quoted context omitted.
This is basically that but in the opposite direction. It also has the advantage of being able to express validations that you can't express in the type system.
Do you have an example of the kind of validation couldn't be expressed in the type system?
Possibly stupid question, but why does the dog array validate: const dogsList = z.array(dogSchema); dogSchema.parse([ { name: 'Cujo', neutered: null }, { name: 'Fido', age: 4, neutered: true }, ]); // passes Since 'Cujo' doesn't have an age? Assuming it's the same dogSchema as in the previous block, age is required, right? Oh, and a minor typo: This lets you confidently This way you can confidently... .
Whoops! Should be `dogsList.parse(...)`. Also fixed the other typo :) Thanks!!
I'd really like something like a compiler step/plugin to generate the validators from the declared typescript types.
Yeah, that's really something that feels like it should be a part of the language, because it would be so useful!
> Add or rely on run-time type information in programs, or emit different code based on the results of the type system. Instead, encourage programming patterns that do not require run-time metadata.
[1] https://github.com/Microsoft/TypeScript/wiki/TypeScript-Desi...
There is also class-validator, which I've used and I find elegant and working well: https://github.com/typestack/class-validator
I don't love the class-based declarations: it's a bit verbose and doesn't allow you to use things like the spread operator to "mix in" fields into objects. There's also some redundancy required for basic types:
@IsString
firstName: string;
But their validation built-ins go way beyond Zod (IsEmail, Min, Max, Contains, native Date support, etc). Thanks for sharing.
Possibly stupid question, but why does the dog array validate: const dogsList = z.array(dogSchema); dogSchema.parse([ { name: 'Cujo', neutered: null }, { name: 'Fido', age: 4, neutered: true }, ]); // passes Since 'Cujo' doesn't have an age? Assuming it's the same dogSchema as in the previous block, age is required, right? Oh, and a minor typo: This lets you confidently This way you can confidently... .
Whoops! Should be `dogsList.parse(...)`. Also fixed the other typo :) Thanks!!
Wow I made the same thing that I put v1 up a couple days ago. https://github.com/tetranoir/presi A main difference is I tried to get rid of having a separate line to create the Type and I tried to get rid of having to learn a new libary's api as much as possible.
Earlier quoted context omitted.
Whoops! Should be `dogsList.parse(...)`. Also fixed the other typo :) Thanks!!
I don’t want to derail the thread, but just a heads up: the layout is very broken on my phone (iPhone). The text is clipped on the left side which basically makes the article unreadable!