Warren Bickley

I had a stab at this, not sure it's necessarily right or in the right place though given that I have attached the info to `issue` as opposed to context......

Similar issues and conversations include #1154 #901 #456

Hey @Svish 👋 I believe it is on certain issues, but I think only ever equal to `"array" | "string" | "number" | "set"` as opposed to the full Zod...

To be honest, the existing type would probably be enough to cover my needs too. However, it means you have to conditionally check the issue code in order to satisfy...

@Svish has summed up my thoughts better than I could have too. I think keeping Zod focussed is definitely sensible, but as it stands it's not really flexible enough (I...

@colinhacks would it be fair to me to say that based on the signature of "RawCreateParams" I can only set the invalid type and required error strings? In order to...

Well, I attempted to think about this a bit differently but feel I failed. https://gist.github.com/WazzaJB/5700b07c6bcf0c5847a2a50051f68310 Use "label" instead of Zod and set the error map within there, doesn't work though...

Just to add a note here for anyone else battling this issue. If you have already run the migrate command, applying the patch above will still yield the same error...

The solutions I found across the various tickets here didn't work for me unfortunately, but appreciate everyones efforts to come up with a solution. I had to extend the prettier...

In that case I shall raise a PR and try to prepare a codespace you can trial this in :)