feat(form): Introduce useForm and useFormControl composable

[rdjanuar]

🔗 Linked issue

Resolves #3876

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@4755

commit: 1c74a41

[rdjanuar]

This PR still mising some task, If there are any additions, they can be added here.:

• Create Documentation
• Integrate Unit test
• generate state base on schema

Maybe i need help to verify my typescript, cc @sandros94

[rdjanuar]

we cannot modify target because is read-only

https://developer.mozilla.org/en-US/docs/Web/API/Event/target

[sandros94]

@romhml haven't we discussed this before? It does ring a bell in my head 🤔

[sandros94]

This PR still mising some of task, If there are any additions, they can be added here.:

• Create Documentation
• Integrate Unit test

Maybe i need help to verify my typescript, cc @sandros94

Will happily take a look in a couple of days, as I'm on vacation and with limited connectivity

[rdjanuar]

I’ve finished handling state generation based on schema.

here how i implement it:
Zod: needs special handling since we have to parse every value. Luckily there’s already a solution — I copied the init function from zod-empty

Valibot: users can use the built-in getDefaults()

Yup: supports .getDefault() on schema, so I handle this internally.

Superstruct: no built-in way for defaults, so users will need to provide their own defaultValues.

[sandros94]

thanks @rdjanuar, I've been following some of the commits, but unfortunately I got buried with work since I came back from vacation. Will hopefully take a look at least at types during the weekend.

Just a small note: while I completely agree on a useForm composable, I'm still not fully convinced to have a built-in parser for validation schemas, because they would all require different adapters and as you noticed not all of them do provide utils for even defaults. But this is more of a personal opinion

[rdjanuar]

Thank you @sandros94 for taking the time to review my useForm implementation. you right its' require a lot effort to handle parsing on each library schema but my current implementation is just improve DX especially on zod because every time i interact with Form component i should add every single field on state and i'ts taking a lot of time