fix(InputMenu/Select/SelectMenu): exclude cosmetic items from model value type

[sandros94]

Some components like InputMenu, SelectMenu and Select support for items that are purely cosmetic like type: 'label' and type: 'separator'.

This causes a waterfall of type issues

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates type handling and narrow-cases across input and select components and shared types. Components (Input.vue, Textarea.vue) tighten when modelModifiers.optional can coerce values to undefined by requiring nullable to be false and the current value non-null. Menu/select components (InputMenu.vue, Select.vue, SelectMenu.vue) introduce an internal ExcludeItem type and thread it through props, emits, slots, and helper typings to exclude label/separator item shapes from model values. Utility types in utils.ts are refactored to add an optional O parameter propagated through GetItemValue, GetModelValue, and GetModelValueEmits. input.ts adjusts ModelModifiers conditional defaults.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is related to the changeset, explaining the motivation behind excluding cosmetic item types from model-value types to resolve type issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into v4
Title check	✅ Passed	The title accurately reflects the main change: excluding cosmetic items from model value types in InputMenu, Select, and SelectMenu components.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/exclude-known-types-from-model-values

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/runtime/components/SelectMenu.vue (1)

37-38: Naming inconsistency: ExcludeMenuItem here vs ExcludeItem in Select.vue.

Select.vue defines type ExcludeItem = { type: 'label' | 'separator' } while SelectMenu.vue and InputMenu.vue use ExcludeMenuItem. Since these are file-local types with identical shapes, this isn't a bug, but unifying the name (e.g., all ExcludeItem) would reduce cognitive overhead when navigating between components.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@6044

commit: 554507a

[coderabbitai]

🧹 Nitpick comments (1)

src/runtime/components/SelectMenu.vue (1)

37-37: Extract ExcludeItem to shared types.

This type is identically defined in Select.vue, SelectMenu.vue, and InputMenu.vue. Move it to src/runtime/types/utils.ts where the components already import shared generics like GetItemValue and GetModelValue, eliminating duplication and establishing a single source of truth.