Bennett

> How do I get this working now that I have updated to V2, v2.1 is not available on npm yet I think there was a problem generating the new...

This doesn't currently exist because it sometimes worked unreliable - but I'll add it in the future. In the meantime you can hook into `react-hook-form` directly, it should work like...

I don't think I fully understand you issue - I tried running this code but the values I got looked correct: https://codesandbox.io/p/sandbox/autoform-mui-demo-3pjwvr

As described at https://autoform.vantezzen.io/docs/react/getting-started#nextjs-and-rsc, AutoForm is intended to be used in Client-side component since there had been problems with serializing zod schemas otherwise and handling of callbacks. I'll see if...

I think it would be good to add support for a `formRef` prop to allow doing this easily. For now you can try using the "onFormInit" prop to get access...

I think conceptually this is very similar to the new `@autoform` libraries, right? Both systems map the zod types to rendering specific form elements - just with a bit of...

The rebuild didn't work for me because I got this message: > The following dependencies have build scripts that were ignored: @parcel/watcher, @swc/core, esbuild, lmdb, msgpackr-extract, sharp To allow the...

How would you want literals to behave? And do you have specific unions that you need support for? I think adding general support for unions could be difficult since having...

Looks interesting - but yes this should definitely opt-in and not pollute the zod prototype by default. I think in some use-cases the schemas are automatically generated so they can't...

I experimented with this a bit but - at least for me - changing the zod prototype directly seems hacky, especially as it's not officially supported by zod and creates...