fix(components): broken types for update:model-value event

[J-Michalek]

🔗 Linked issue

Resolves: #4852

❓ 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

I've omitted the update:modelValue event from the FileUploadEmits interface used in defineEmits as the type seems to break when used in both defineModel and defineEmits at the same time.

📝 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@4853

commit: 2c43cd7

[benjamincanac]

I believe it would be easier to just remove it from the FileUploadEmits interface, what do you think?

Also, I noticed we have the same error in the Slider component and maybe others 🤔

[J-Michalek]

@benjamincanac Yeah I also saw it in more components, but I did not try if it works there... I also saw it used together with useVModel and though it might work alright with it, I would just remove it from the interface and let defineModel macro take care of it, but I am not sure if someone actually needs to be able to have the v-model events defined in the interface.

[benjamincanac]

I would only remove it when used with defineModel, not useVModel (which is used in some components to handle defaultValue). It was mostly used for the Emits section in the docs but it's picking up the one from defineModel correctly now.

[J-Michalek]

Sure, I will take care of it.

[benjamincanac]

@J-Michalek I took the liberty to push to your PR and rename at the same time some events for consistency, let me know what you think!

[J-Michalek]

LGTM!