Skip to content

Conversation

@romhml
Copy link
Member

@romhml romhml commented Nov 14, 2025

This PR is a follow-up from #5379 to refactor and simplify the Form component by using Formwerk to handle the core validation and form logic.

πŸ”— Linked issue

❓ 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.

@benjamincanac
Copy link
Member

Shall we merge this into #5379?

Comment on lines +166 to +173
disabled,
required: props.required,
controlType: 'UFileUpload'
})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@romhml What do you think about abstracting useCustomControl<T> inside of the useFormField composable?

That way we can better standardize the setting of touched, blurred and dirty fields when users implement their own custom form fields?

I'm thinking something like this: https://github.com/nuxt/ui/blob/4dea1067caa0d3e973d329a365945dc208c163e8/src/runtime/composables/useFormField.ts

@genu
Copy link
Member

genu commented Nov 25, 2025

Shall we merge this into #5379?

I think we'd close the other in favor of this, ultimately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants