What led you to that conclusion?

dsabanin 5 hours ago | parent | next [-]

Zod's validation errors are awful, the json schema it generates for LLM is ugly and and often confusing, the types structures Zod creates are often unintelligible in the and there's even no good way to pretty print a schema when you're debugging. Things are even worse if you're stuck with zod/v3

	▲	sesm 4 hours ago \| parent \| next [-]
		What's wrong with Zod validation errors?
	▲	light_hue_1 4 hours ago \| parent \| prev [-]
		None of this makes a lot of sense. Validation errors are largely irrelevant for LLMs and they can understand them just fine. The type structure looks good for LLMs. You can definitely pretty print a schema at runtime. This all seems pretty uninformed.

▲

nerdponx 6 hours ago | parent | prev | next [-]

And what makes this different? What makes it LLM-native?

▲

podperson 5 hours ago | parent [-]

It generates schemas that are strict by default while Zod requires you to set everything manually.

This is actually discussed in the linked article (READ ME file).

▲

halayli 4 hours ago | parent [-]

That's not true based on zod docs. https://zod.dev/api?id=objects

most of the claims you're making against zod is inaccurate. the readme feels like false claims by ai.

	▲	podperson 2 hours ago \| parent [-]
		It seems to be true to me. And aside from the API stuff (because I am far from an expert user of Zod) all of this has been carefully verified.

▲

podperson 5 hours ago | parent | prev [-]

1. Zoe’s documentation, such as it is 2. Code examples