fix(Form): correct error filtering logic during validation

[rdjanuar]

🔗 Linked issue

Resolves #4455

❓ 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@4843

commit: 5cc82a8

[romhml]

@rdjanuar do you mind explaining the changes? And possibly add some tests to prevent regressions?

[rdjanuar]

Okay @romhml, Here's a quick breakdown of the fix:

• My changes do two main things. First, I made the validation faster on big forms by switching from an array lookup
  (names.some()) to using a Set, which is much more efficient.
• Second, I fixed a tricky race condition where an error could reappear right after being cleared. I changed the
  order of operations to call await getErrors() first. This gives the clear() function time to finish its job before
  the validation continues, which stops the cleared error from coming back.