Order of optional and nullable matters about zod-to-json-schema

[urugator]

If I read the sources correctly, parsers like nullable/union try to simplify the output whenever the inner types are primitive, but the inner type in this case is optional and the algo doesn't try to look further at it's inner type...

OT: any reason why this check:

zod-to-json-schema/src/parsers/nullable.ts

Lines 20 to 22 in cd6fac7

	["ZodString", "ZodNumber", "ZodBigInt", "ZodBoolean", "ZodNull"].includes(
	def.innerType._def.typeName
	) &&

doesn't use in primitiveMappings like here:
https://github.com/StefanTerdell/zod-to-json-schema/blob/master/src/parsers/union.ts#L51
??

[urugator]

The application order in case of nullish was actually already fixed in zod, but it's not released yet:
colinhacks/zod@0c0e495

[StefanTerdell]

Closing this since Zod is a peer dependency and this can be fixed by just bumping it.