\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```",[3064,3067],{"name":3065,"color":3066},"enhancement","a2eeef",{"name":3041,"color":3042},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.77732414,{"description":3074,"labels":3075,"number":3083,"owner":3027,"repository":3047,"state":3084,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3076,3077,3080],{"name":3038,"color":3039},{"name":3078,"color":3079},"documentation","0075ca",{"name":3081,"color":3082},"duplicate","cfd3d7",2429,"closed","DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.724958,{"description":3090,"labels":3091,"number":3093,"owner":3027,"repository":3094,"state":3084,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### 📚 Is your documentation request related to a problem?\n\nI want to change `fetchproirity=\"low\"` to `fetchpriority=\"hight\"`.\n\nI made use of the Google Tag Manager script from the Script Registry.\n\n\u003Cimg width=\"672\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/74e8a344-e908-44f6-b061-0982d8e4990a\" />\n\n\n### 🔍 Where should you find it?\n\nI can't find it in the docs, but if you can change the `fetchpriority`, it should be in on the Google Tag Manager page on de Scripts Registry.\n\n=> [scripts.nuxt.com/scripts/tracking/google-tag-manager](https://scripts.nuxt.com/scripts/tracking/google-tag-manager)\n\n### ℹ️ Additional context\n\n_No response_",[3092],{"name":3078,"color":3079},338,"scripts","How can I change fetchpriority from 'low' to 'high' (Google Tag Manager)","2024-12-17T10:34:14Z","https://github.com/nuxt/scripts/issues/338",0.7397693,{"description":3100,"labels":3101,"number":3102,"owner":3027,"repository":3103,"state":3084,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Describe the bug\r\n\r\n` WARN The glob option \"as\" has been deprecated in favour of \"query\". Please update as: 'raw' to query: '?raw', import: 'default'.`\r\n\r\nnuxt-icon.vue:23\r\n```js\r\n const iconsImport = import.meta.glob('assets/icons/**/**.svg', {\r\n as: 'raw',\r\n eager: false\r\n })\r\n```\r\n\r\nWhen removing the { as: `raw` }, the error disappears.",[],145,"icon","import.meta.glob as: 'raw' fails","2024-04-12T06:03:06Z","https://github.com/nuxt/icon/issues/145",0.74539036,{"description":3109,"labels":3110,"number":3114,"owner":3027,"repository":3047,"state":3084,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nChart is one of many things found when developing a statistics such as in dashboard admin. It would be good if nuxt ui have this component.\n\n### Additional context\n\n_No response_",[3111,3112,3113],{"name":3081,"color":3082},{"name":3065,"color":3066},{"name":3041,"color":3042},2673,"Chart component","2024-11-18T08:33:07Z","https://github.com/nuxt/ui/issues/2673",0.7498951,{"description":3120,"labels":3121,"number":3124,"owner":3027,"repository":3028,"state":3084,"title":3125,"updated_at":3126,"url":3127,"score":3128},"\n",[3122],{"name":3038,"color":3123},"ff281a",464,"[Milkdown] Remove text zone in component when no slots","2023-06-06T12:14:52Z","https://github.com/nuxt/nuxt.com/issues/464",0.7533025,{"description":3130,"labels":3131,"number":3124,"owner":3027,"repository":3132,"state":3084,"title":3133,"updated_at":3134,"url":3135,"score":3128},"Originally reported by nuxt/test-utils#329, when having multiple `.test` files, jest runs them in parallel. If two depending on a single fixture and need build, this causes issues. Some options are:\r\n\r\n- Using run-in-band to disable parallel run\r\n- Using a lock-file so one test awaits on others during build\r\n- Using random build ids for `buildDir`\r\n- Using mfs (#49) for building in mem (considering all internals can support)\r\n\r\n",[],"test-utils","fix: build conflict between multiple tests","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/464",["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foi__BUfUC6hBZFvZRu8W5ix5-ff7fFTym6d6quvTX-M":-1},"/nuxt/icon/335"]