`custom` should exist on the method chain instead of only at the root about zod HOT 4 OPEN

Is this what you are looking for?

const numPlayersBase = z.number().int().min( 2 ).max( 100 )
type NumPlayers = z.infer<typeof numPlayersBase>
type RealNumPlayers = IRange<2, 100> // 2 | 3 | 4 | ... | 100
const numPlayers = z.custom<RealNumPlayers>( data => numPlayersBase.safeParse( data ).success )

If you found my answer satisfactory, please consider supporting me. Even a small amount is greatly appreciated. Thanks friend! 🙏
https://github.com/sponsors/JacobWeisenburger

from zod.

Hi Jacob,

Your answer is great in that it does indeed leverage the Zod validation. And one could easily add their own logic afterward.

However, I still think there is room for improvement. There would be no need to run base.SafeParse at all if custom existed on the method chain. In other words:

type NumPlayers = IRange<2, 100>; // 2 | 3 | 4 | ... | 100
const numPlayersBase = z.number().int().min(2).max(100);
const numPlayers = z.custom<RealNumPlayers>(data => numPlayersBase.safeParse(data).success);

versus

type NumPlayers = IRange<2, 100>; // 2 | 3 | 4 | ... | 100
const numPlayers = z.number().int().min(2).max(100).custom<NumPlayers>();

The second snippet is more concise and easier to read!

from zod.

So I'm gathering that you are wanting this to be a new feature instead of asking for a workaround, is that correct?

from zod.

Yes, this is a feature request issue.

from zod.