Scott Trinh

@colinhacks > For the sake of future-proofing Zod, I think we should assume that strict mode is enabled, and none of its individual components have been disabled. This is my...

I think `fallback` would be a nice feature for sure! FWIW, Zod actually _does_ have a `z.custom` schema that is just undocumented. It takes a `(unknown) => boolean` function.

I would say that the goal of Zod is the ensure that the data you get after calling `parse` is precisely in the format you expect based on the inferred...

@cpitclaudel I'd love to help with this. Is there anything specific I can do to help move this forward?

Something that I've been working on in my own project is migrations. That has been [historically](https://www.inkandswitch.com/cambria/#augmenting-data) [challenging](https://riffle.systems/essays/prelude/#migrations-are-a-challenge) and I wonder what opportunities thinking about this abstraction can provide us with...

I would just like to "me too" on the idea that shipping code to the browser is really a bundler concern, and the future will be rich with bundling solutions...

Is there an issue with using `path` here? I don't think there is a default message we can use that will satisfy all use cases since Zod is not a...

> If what i have listed above is the stance of devs, than maybe closing as wontfix, optionally with a brief explanation, would be preferable to the stalebot being unleashed,...

Thanks @AustinShelby for providing the working code, that does seem to be the correct way to address the original question.

It also makes returning functions from a `match` a little trickier (impossible?), right? Not sure it's worth it to save the `() =>`, but you could always write your own...