\n```\n\n**Possible solutions:**\n\n1. Make a new label prop that accepts a function, so values can be compound:\n\n```ts\n\u003CUSelectMenu :label=\"(item) => item.firstName + ' ' + item.lastName\"\n```\n\n2. Optionally make a slot to customize the labels: \n```vue\n\u003CUSelectMenu>\n \u003Ctemplate #label=\"{ item }\">\n {{ item.firstName }} \u003Cspan class=\"text-highlighted\">{{ item.lastName}}\u003C/span>\n \u003Cspan class=\"text-xs text-muted\">#{{ item.customerId }}\u003C/span>\n \u003C/template>\n\u003C/USelectMenu>\n```\n\nP.S. the prop `labelKey` is not documented https://ui.nuxt.com/components/select-menu#props\n",[3137,3140,3143],{"name":3138,"color":3139},"enhancement","a2eeef",{"name":3141,"color":3142},"v3","49DCB8",{"name":3144,"color":3145},"triage","ffffff",4581,"nuxt","ui","open","SelectMenu: Compound label","2025-07-23T16:38:06Z","https://github.com/nuxt/ui/issues/4581",0.7347953,{"description":3155,"labels":3156,"number":3160,"owner":3147,"repository":3148,"state":3149,"title":3161,"updated_at":3162,"url":3163,"score":3164},"### Description\n\nOptions in `SelectMenu` might need a description below the title e.g. like the watch dropdown on github:\n\n\u003Cimg width=\"362\" height=\"378\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/78093701-742b-49ad-8b60-e26435a3bca5\" />\n\nIt can be worked around using `item-label` slot, but it would be nice if developer can use `items` props only to implement it for simpler way.\n\nBelow, I have tried to create it using Reka UI `combobox` component, the component used by SelectMenu.\n\n\u003Cimg width=\"329\" height=\"460\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e5cda771-3f8e-4369-bb3b-d5159f84d425\" />\n\n### Additional context\n\n_No response_",[3157,3158,3159],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4661,"SelectMenu: add description props to show text below title","2025-08-06T02:19:32Z","https://github.com/nuxt/ui/issues/4661",0.735004,{"description":3166,"labels":3167,"number":3172,"owner":3147,"repository":3148,"state":3149,"title":3173,"updated_at":3174,"url":3175,"score":3176},"### Environment\n\n- OS: Windows\n- Nuxt: v4.0.3\n- Node: v22.14.0\n\n### Version\n\nv4.0.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-gtu8vgxz?file=app.vue\n\n### Description\n\nThe USelectMenu component does not block form validation even when setting the required prop.\nI though this was a bug since the USelect component instead correctly blocks validation when setting the required prop.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3168,3171],{"name":3169,"color":3170},"bug","d73a4a",{"name":3144,"color":3145},4757,"USelectMenu required prop is not blocking form validation","2025-08-15T10:52:46Z","https://github.com/nuxt/ui/issues/4757",0.73639804,{"description":3178,"labels":3179,"number":3182,"owner":3147,"repository":3148,"state":3149,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Description\n\nDear Contributors,\n\nNuxtUI has been a great help in my app development. Thank you very much.\n\nI would like to request the addition of a new feature. I would appreciate your consideration.\n\n\nCommon search engines provide a search bar with a suggestion feature.\nSelecting a keyword from the provided suggestions is optional; if a user does not select a suggestion, the content they have entered takes precedence.\n\nHowever, the current InputMenu specifications automatically select the first item on the list if the user doesn't make a selection, overwriting the user's input with that value.\nIt would be useful if there were a feature that limited the overwriting of user input to only cases where the user explicitly selects an item from the list.\n\nThank you.\n\n### Additional context\n\n_No response_",[3180,3181],{"name":3138,"color":3139},{"name":3144,"color":3145},4717,"InputMenu want to selection to optional","2025-08-12T05:38:55Z","https://github.com/nuxt/ui/issues/4717",0.7470045,{"description":3188,"labels":3189,"number":3193,"owner":3147,"repository":3148,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Description\n\nNeed to have the ability to provide a callback function to onRemoveTag when selecting multiple items to be able to customize its behavior.\n\n### Additional context\n\nIn my use case for example I have an InputMenu with Multiple selections the items list contains values that fall under multiple categories for example A, B, and C with the ability to search for any of them in the same InputMenu, so the list of items looks something like this:\n- A: A1\n- A: A2\n- B: B5\n- C: C7\nthe state is then stored in a pinia store based on the category onSelect, e.g. `if (key == \"A\") store.listA.push(item.value)` when I click on the remove tag the v-model value is updated, but I have no idea which category was it from, meaning I will have to check all the items to know which state to update since they are actually separate.",[3190,3191,3192],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4463,"closed","[InputMenu] ability to control behavior of onRemoveTag","2025-07-16T20:28:46Z","https://github.com/nuxt/ui/issues/4463",0.6901558,{"description":3200,"labels":3201,"number":3204,"owner":3147,"repository":3148,"state":3194,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Description\n\nUSelect displays the label of the selected value. It might be interesting to add a slot to display another key when item is an object instead of the chosen label for some use case.\n\nMy own use case is picking the language :\n\n```\nconst items = [\n { value: 'en', label: 'English' },\n { value: 'fr', label: 'Français' },\n (...)\n]\n```\n\nMy open selection would display flags and labels, but once selected, the component would only display the value ('en' or 'fr' or ...). Could be the icon as well.\n\nProposal :\n\nselectLabelKey : When items is an array of objects, select the field to use as the label for the picked value on the base component (instead of labelKey)\n\n### Additional context\n\n_No response_",[3202,3203],{"name":3138,"color":3139},{"name":3141,"color":3142},4157,"USelect base text display","2025-05-23T12:25:54Z","https://github.com/nuxt/ui/issues/4157",0.6981883,{"description":3210,"labels":3211,"number":3214,"owner":3147,"repository":3148,"state":3194,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Description\n\nWhen using \u003CUNavigationMenu> with onSelect (instead of to), there's no way to manually set the active state on items. It would be helpful to support an active prop or a value binding (like in buttons #3417) to reflect the selected state visually.\n\n### Additional context\n\n_No response_",[3212,3213],{"name":3138,"color":3139},{"name":3141,"color":3142},4185,"Allow `active` style on `UNavigationMenu` items when using `onSelect`","2025-05-19T15:38:25Z","https://github.com/nuxt/ui/issues/4185",0.7082749,{"description":3220,"labels":3221,"number":3225,"owner":3147,"repository":3147,"state":3194,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[3222],{"name":3223,"color":3224},"pending triage","E99695",28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.7142208,{"description":3231,"labels":3232,"number":3235,"owner":3147,"repository":3236,"state":3194,"title":3237,"updated_at":3238,"url":3239,"score":3240},"Shortcut for the \"Save\" button.",[3233],{"name":3138,"color":3234},"1ad6ff",657,"nuxt.com","[Project] Support `CMD+S` to commit","2023-02-15T12:32:41Z","https://github.com/nuxt/nuxt.com/issues/657",0.71498924,{"description":3242,"labels":3243,"number":3248,"owner":3147,"repository":3148,"state":3194,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Description\n\nHey there!\n\nI am currently doing migration of https://www.nuxt-commerce.dev/ from Nuxt UI 2->3 (it was so good experience - kudos to you!).\n\nI finished migrating almost everything apart from one thing - the Select component that has Nuxt Links inside. Basically the NuxtLink does not seem to work - the page is not changing after clicking (while the selected value is correctly updated to the clicked one. Do you know what could be the issue?\n\nThe code I use looks like this:\n\n```html\n\u003Ctemplate>\n \u003CUSelect\n v-model=\"selected\"\n value-key=\"value\"\n :items=\"selectOptions\"\n >\n {{ selected }}\n \u003Ctemplate #item=\"{ item }\">\n \u003CNuxtLink\n :to=\"`/collection/${item?.to}`\"\n >\n \u003Cp>{{ item?.value }}\u003C/p>\n \u003C/NuxtLink>\n \u003C/template>\n \u003C/USelect>\n\u003C/template>\n\n\n\u003Cscript setup lang=\"ts\">\nconst selectOptions = computed(() => {\n return props.collections?.edges.map(({ node }) => ({\n value: node.title,\n to: node.handle,\n }))\n})\n\nconst selected = ref(\n selectOptions.value?.find(\n option => route.params.handle && option.to === route.params.handle[0],\n )?.value,\n)\n\u003C/script>\n```",[3244,3247],{"name":3245,"color":3246},"question","d876e3",{"name":3141,"color":3142},3443,"Does Select work with NuxtLink/UI Link?","2025-03-04T09:18:16Z","https://github.com/nuxt/ui/issues/3443",0.72095096,["Reactive",3254],{},["Set"],["ShallowReactive",3257],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fnb-ubhPAEozelxoD5LB6KGjB3MPnzQuHpdiwo0T88-c":-1},"/nuxt/ui/4647"]