Bennett
Bennett
Here's how this could look like: https://github.com/vantezzen/auto-form/tree/feat/superrefine#field-configuration
For components there is no difference to the old implementation as the embedded fieldConfig extracted and merged to the fieldConfig prop before rendering: https://github.com/vantezzen/auto-form/blob/e7a6a27e2218223a2bdc684bf043eb3c7f95c6dc/src/components/ui/auto-form/index.tsx#L63 The superRefine function is just an...
I think maybe using the key makes more sense? I feel like `label` sounds more like a user-facing/display-only property than a unique way to identify values? And IIRC zod is...
Yes that would be good to have full consistency!
Oh I didn't know that about joi and yup! That's difficult, I think at the end zod expects the `key` as the value otherwise the schema is invalid, right?
Sounds very interesting, would be good to solve all these issues with one fix! Feel free to move on with this
[BUG] Error: Could not resolve module "node:module" in jiti after upgrading to Tailwind v4 in Plasmo
For anyone unfamiliar with patching in pnpm, here's a more detailed guide for Plasmo and Tailwind 4: https://gist.github.com/vantezzen/f799643aebbfd5522ce87bababb85c5d
What error does this fix? Please use the provided eslintrc instead of your tab formatting
> I want to use another AutoForm inside the AutoForm component Could you describe the use-case where this is useful? Kind of sounds like that might be better solved with...
Thank you for the feedback - I'll work on a migration guide! As for formStates, AutoForm removed the dependency on the react-hook-form lib since that complicated implementing some features. Due...