\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[2872,2873],{"name":2853,"color":2854},{"name":2856,"color":2857},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.801999,{"description":2880,"labels":2881,"number":2885,"owner":2862,"repository":2863,"state":2864,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Description\n\nHello,\n\nI've spent the last couple of hours trying to implement right-click functionality on UTable rows. I've reviewed existing issues but couldn't find a solution that fits this need.\n\nWhat I want to achieve is to show a UContextMenu with actions related to the clicked row when the user right-clicks on it.\n\nCurrently, there is no way I could find to detect right-click events on individual rows along with their row data. If UTable had a #row slot or a dedicated @click.right event that provides the clicked row’s data, this would be easily achievable.\n\nIf there is any workaround or method to implement this right-click behavior on rows with access to row data, I would really appreciate if someone could share it.\n\nThank you!\n\n\n\n### Additional context\n\n_No response_",[2882,2883,2884],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2859,"color":2860},4259,"Add support for @click.right event on UTable rows to enable context menus","2025-05-30T14:35:19Z","https://github.com/nuxt/ui/issues/4259",0.80734605,{"description":2891,"labels":2892,"number":2900,"owner":2862,"repository":2863,"state":2901,"title":2902,"updated_at":2903,"url":2904,"score":2905},"",[2893,2896,2897],{"name":2894,"color":2895},"bug","d73a4a",{"name":2856,"color":2857},{"name":2898,"color":2899},"reka-ui","56d799",2257,"closed","[InputMenu/SelectMenu] Combobox `default-value` does not seem to work","2025-03-27T15:24:39Z","https://github.com/nuxt/ui/issues/2257",0.72144103,{"description":2907,"labels":2908,"number":2918,"owner":2862,"repository":2863,"state":2901,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Description\n\nCurrently, I want to use the InputMenu for URL suggestions. The user can choose whether they want to select one of the suggestions or enter their own URL. There are several InputMenus, which means that the user usually wants to jump to the next field using the tab key. \n\nHowever, this is not so easy with the InputMenu. With `create-items`, the field expects a click or enter to be entered. There is no autocreate. \n\nI have also tried using `update:search-terms`, which worked well as long as the user treated it as a pure input field. However, in this case, no suggestions appear. And if the user selects a suggestion, the VModel is also empty – more precisely, it gets a value and is deleted shortly afterwards.\n\nTherefore, it would be desirable if create-items could be set to transfer the input to the V-Model immediately, or if there was a general mode in which the input field treats the suggestions as optional.\n\n\n\n### Additional context\n\n_No response_",[2909,2910,2913,2914,2915],{"name":2853,"color":2854},{"name":2911,"color":2912},"needs reproduction","CB47CF",{"name":2856,"color":2857},{"name":2859,"color":2860},{"name":2916,"color":2917},"closed-by-bot","ededed",4106,"InputMenu with Autocreate","2025-05-18T02:13:24Z","https://github.com/nuxt/ui/issues/4106",0.7739675,{"description":2924,"labels":2925,"number":2929,"owner":2862,"repository":2863,"state":2901,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Description\n\nI'm making a search menu with an http call, where you can select multiple items, and all the filtering is done on the backend\n\nSo I dont need the filtering fuse does, and I would appreciate if it could be disabled so it doesnt interfere with the results from my backend\n\n### Additional context\n\n_No response_",[2926,2927,2928],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2859,"color":2860},4061,"[CommandPalette] Disable fuse integration","2025-05-04T10:41:03Z","https://github.com/nuxt/ui/issues/4061",0.774826,{"description":2935,"labels":2936,"number":2939,"owner":2862,"repository":2940,"state":2901,"title":2941,"updated_at":2942,"url":2943,"score":2944},"`ProjectModalBranches` and `ProjectModalFiles` share the same logic for combox, the idea is to create a component `components/project/ProjectCombobox.vue` that will handle the logic:\n\n**Props**\n\n- `itemsLabel`\n- `items`\n- `recentItemsLabel` (default `Recent`)\n- `recentItems`\n- `actionsLabel` (default `null`)\n- `actions`",[2937],{"name":2853,"color":2938},"1ad6ff",362,"nuxt.com","Refactor command palette logic into one component","2023-02-15T12:32:14Z","https://github.com/nuxt/nuxt.com/issues/362",0.7755546,{"description":2946,"labels":2947,"number":2950,"owner":2862,"repository":2863,"state":2901,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nCurrently, we are unable to manually trigger the searchable method. Lets assume i have one `USelectMenu` component that list all `Parent` object and a second `USelectMenu` that list all `Children` of the selected `Parent`. Currently, when the `USelectMenu` component i mounted, the search query is executed even if the parent object is not yet selected.\n\nIt would me very useful to be able to manually trigger the search query method to populate the `USelectMenu` options.\n\nIs there any alternative to do it using the current behavior ? Maybe using a `ref` or something ?\n\n### Additional context\n\n_No response_",[2948,2949],{"name":2853,"color":2854},{"name":2859,"color":2860},2882,"USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.77657896,{"description":2956,"labels":2957,"number":2960,"owner":2862,"repository":2863,"state":2901,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.4.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: bun@1.2.5\n- Builder: -\n- User Config: devtools, modules, imports, components, css, compatibilityDate, experimental, future\n- Runtime Modules: @nuxt/ui@3.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/recursing-browser-klwx46\n\n### Description\n\nWhen a `SelectMenu` is wrapped in a custom component which is then consumed by `FormField` validation is triggered for an instant before the component goes back to its valid state.\n\nI've tried to debug a bit and I think it's related to the fact that the `SelectMenu` uses `Input` and that input is firing a `change` event because it uses `useFormField`, even though that particular input should not be considered the \"form field\" in this instance.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/75e8c84f-612e-48f0-bf9e-dcc1fe95ffcd\n\nI'd like to open a PR and fix this myself but I'm not sure what the best approach it. Maybe `Input` could take a prop that allows it to not fire form events? i.e. `ignore-form-events=\"true\"` so the SelectMenu would use it. This could also apply for other components that use primitive form inputs inside them (Command, InputMenu) etc.\n\n### Logs\n\n```shell-script\n\n```",[2958,2959],{"name":2894,"color":2895},{"name":2856,"color":2857},3736,"[USelectMenu] Validation events are triggered before change when wrapped in a custom component","2025-05-14T17:24:48Z","https://github.com/nuxt/ui/issues/3736",0.7841311,{"description":2966,"labels":2967,"number":2972,"owner":2862,"repository":2863,"state":2901,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### 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```",[2968,2971],{"name":2969,"color":2970},"question","d876e3",{"name":2856,"color":2857},3443,"Does Select work with NuxtLink/UI Link?","2025-03-04T09:18:16Z","https://github.com/nuxt/ui/issues/3443",0.794075,["Reactive",2978],{},["Set"],["ShallowReactive",2981],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPtbU_nKI3FkjnQePtBRZeDUgQfRyNb2HmeuqBikMaxk":-1},"/nuxt/ui/4239"]