fix(Form): added name to fieldState

[hrynevychroman]

update useFormField function fieldState definition

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ 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

On my own project, I had a problem with useFormField; there are no changes inside the FormControl component, aria-invalid property remains unchanged, but errors were inside the errors object returned from useForm vee-validate. Some time was needed to find the problem, and it was inside the useFormField function, where fieldState was just generated with useFieldError, for example, without passing the name inside. After just adding name, everything worked fine. This occurred on custom phone input with select and input that only receives the :name property from the parent slot.

📸 Screenshots (if appropriate)

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

[sadeghbarati]

Right, since we mostly using useForm instead of <Form> component

useIsFieldValid
resolveFieldOrPathState might not work perfectly

Passing name to these functions is LGTM

[hrynevychroman]

@sadeghbarati thanks! Who needs to squash and merge? Can I do this?

[sadeghbarati]

Sure do it yourself 🥇 squash it