Switch from joi to zod

[luixo]

While working types unification I stumbled upon Joi library downsides types-wise.
I think we should consider moving to another library which would give us more strict types on endpoint inputs (and maybe outputs).

So what's missing?

• type inference - I have to put types manually to Joi.object
• literal union doesn't work - the type is any
• array doesn't work - types of the items are lost
• discriminated union are broken in a way that they don't produce any - one would usually use Joi.alternatives to run the validation though the types expect Joi.SchemaMap.

I would suggest us moving to zod, I used it in explorer and a few pet projects and value it a lot. I open to other suggestions as well.

[mpeterdev]

already have a ticket for this 😄
#78

[luixo]

Should we keep the discussion here as I pointed out specific details or in the #78 because it has precedence? :)

[mpeterdev]

condensing here since you provided more details 👍

[luixo]

As for a new name of the issue - do we agree on zod, can we implement that yet?

[mpeterdev]

yep, if you have had good experiences with it then let's go for it