Romain Hamel

Thanks, I understand. We can close this PR then, I'll work on implementing it using `/__nuxt_component` in a new one.

@danielroe I've been looking into implementing your suggestion, quick question, would that be OK to rely on the [`components.json` template](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/components/templates.ts#L141) to resolve components path in the SingleRenderer? This means that...

The PR is ready! I've put some efforts in generalizing the implementation because I think this can be made into a standalone module. I'll look into it soon 😄. I...

Not yet, I'll tackle this one soon

We rely on zod's path attribute to map each errors to a `FormGroup` using it's name attribute. When validating arrays, `zod` appends the index to the path of the element,...

Or we might able to add a prop to the `FormGroup` with a pattern instead of a string to match errors, I'll explore this solution!

Not sure I understand the issue here, errors are updated after interacting with the inputs in the reproduction you provided. Errors are updated on submit or input events. What behaviour...

This is expected, we only update errors for the input that has been interacted with. If you want to tie the validation for these three inputs you have to group...

It won't be possible to set different label with the example I gave you. Another work around would be to use `form.setErrors` in the validate function to update the error...

Closing this since validating the entire form on each input event would introduce too much noise. If needed you can trigger the validation using the validate function on an input's...