\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```",[3039,3040],{"name":3020,"color":3021},{"name":3023,"color":3024},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.801999,{"description":3047,"labels":3048,"number":3056,"owner":3029,"repository":3030,"state":3057,"title":3058,"updated_at":3059,"url":3060,"score":3061},"",[3049,3052,3053],{"name":3050,"color":3051},"bug","d73a4a",{"name":3023,"color":3024},{"name":3054,"color":3055},"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":3063,"labels":3064,"number":3068,"owner":3029,"repository":3030,"state":3057,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### Description\n\nA ComboBox component with general functionality we need. As implemented in Vuetify ComboBox. https://vuetifyjs.com/en/components/combobox/#api\n\n### Additional context\n\n_No response_",[3065,3066,3067],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4483,"ComboBox component with common functionality as hide-selected, search-input.sync, clearable","2025-07-08T09:40:29Z","https://github.com/nuxt/ui/issues/4483",0.72652864,{"description":3074,"labels":3075,"number":3079,"owner":3029,"repository":3030,"state":3057,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### 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.",[3076,3077,3078],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4463,"[InputMenu] ability to control behavior of onRemoveTag","2025-07-16T20:28:46Z","https://github.com/nuxt/ui/issues/4463",0.7455004,{"description":3085,"labels":3086,"number":3096,"owner":3029,"repository":3030,"state":3057,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### 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_",[3087,3088,3091,3092,3093],{"name":3020,"color":3021},{"name":3089,"color":3090},"needs reproduction","CB47CF",{"name":3023,"color":3024},{"name":3026,"color":3027},{"name":3094,"color":3095},"closed-by-bot","ededed",4106,"InputMenu with Autocreate","2025-05-18T02:13:24Z","https://github.com/nuxt/ui/issues/4106",0.7739675,{"description":3102,"labels":3103,"number":3107,"owner":3029,"repository":3030,"state":3057,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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_",[3104,3105,3106],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4061,"[CommandPalette] Disable fuse integration","2025-05-04T10:41:03Z","https://github.com/nuxt/ui/issues/4061",0.774826,{"description":3113,"labels":3114,"number":3117,"owner":3029,"repository":3118,"state":3057,"title":3119,"updated_at":3120,"url":3121,"score":3122},"`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`",[3115],{"name":3020,"color":3116},"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":3124,"labels":3125,"number":3128,"owner":3029,"repository":3030,"state":3057,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### 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_",[3126,3127],{"name":3020,"color":3021},{"name":3026,"color":3027},2882,"USelectMenu: Manually trigger the search query","2025-05-10T17:19:44Z","https://github.com/nuxt/ui/issues/2882",0.77657896,{"description":3134,"labels":3135,"number":3138,"owner":3029,"repository":3030,"state":3057,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### 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```",[3136,3137],{"name":3050,"color":3051},{"name":3023,"color":3024},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,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPtbU_nKI3FkjnQePtBRZeDUgQfRyNb2HmeuqBikMaxk":-1},"/nuxt/ui/4239"]