\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2953,2954,2957],{"name":2905,"color":2906},{"name":2955,"color":2956},"needs reproduction","CB47CF",{"name":2908,"color":2909},3546,"`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.68338203,{"description":2964,"labels":2965,"number":2973,"owner":2914,"repository":2915,"state":2945,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Description\n\nThanks to the team for the wonderful UI library. I purchased a license for nuxt/ui-pro, but encountered an activation problem - after paying and receiving the key, I could not [activate](https://ui3.nuxt.dev/pro/activate) it, the system gave an error. `[POST] \"https://api.nuxtlabs.com/ui-pro/activate\": \u003Cno response> Failed to fetch`",[2966,2969,2970],{"name":2967,"color":2968},"question","d876e3",{"name":2908,"color":2909},{"name":2971,"color":2972},"pro","5BD3CB",3341,"License key activation error","2025-02-17T12:02:07Z","https://github.com/nuxt/ui/issues/3341",0.6915108,{"description":2979,"labels":2980,"number":2982,"owner":2914,"repository":2915,"state":2945,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Description\n\nI would like to style my Radio component like this -\n\n\nBut Nuxt UI default styling gives me this. Without much ability to customize -\n\n\nI achieved the first styling in a very hacky way. I saw the DOM of the `\u003CURadioGroup>` component and used deep selector to style child tags. Some class selectors that are used are from tailwind like the items-start (styling code in the comment section). Not the best way, but it works.\n\nIs there a more elegant and straightforward way to do this?\n",[2981],{"name":2967,"color":2968},2950,"NuxtUI custom styling of URadioGroup component","2024-12-22T15:40:17Z","https://github.com/nuxt/ui/issues/2950",0.69376725,{"description":2988,"labels":2989,"number":2991,"owner":2914,"repository":2915,"state":2945,"title":2992,"updated_at":2993,"url":2994,"score":2995},"### Description\n\nThe idea is to add a border in the accordion, but it should be dynamic. It should have the same color that the current accordion color. For instance the next code, but it will not convert the classes `border-{color}-500` in `border-red-500` or any other color. \n\n```vue\n\u003CUAccordion\n color=\"red\"\n :ui=\"{\n container: 'mb-0.5 border border-{color}-500 rounded-lg overflow-y-hidden',\n item: {\n base: 'border-t border-{color}-500',\n padding: 'py-1.5 px-2.5',\n },\n default: {\n class: 'ring-0 rounded-none',\n size: 'xl',\n },\n }\"\n :items=\"[{\n label: 'Getting Started',\n content: 'Getting started content',\n }, {\n label: 'Installation',\n content: 'Installation content',\n }, {\n label: 'Configuration',\n content: 'Configuration content',\n }, {\n label: 'Usage',\n content: 'Usage content',\n }]\"\n/>\n```",[2990],{"name":2967,"color":2968},3452,"Custom accordion with border color as the color attribute","2025-03-27T17:43:06Z","https://github.com/nuxt/ui/issues/3452",0.6939188,{"description":2997,"labels":2998,"number":3001,"owner":2914,"repository":2915,"state":2945,"title":3002,"updated_at":3003,"url":3004,"score":3005},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: pnpm@10.8.0\n- Builder: -\n- User Config: css, app, modules, imports, compatibilityDate, sanctum, fileStorage, ssr\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxtjs/i18n@9.5.3, nuxt-auth-sanctum@0.6.6, @vueuse/nuxt@12.8.2, nuxt-file-storage@0.3.0, @nuxtjs/device@3.2.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt UI version 3.0.2\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst model = defineModel()\n\nconst query = ref('')\nconst items = ref([])\n\nconst isOpen = ref(false)\nconst isLoading = ref(false)\n\nconst search = useDebounceFn(async () => {\n if (query.value.length > 1) {\n isLoading.value = true\n\n items.value = (await fetchApi('categories?q=' + query.value)).data\n\n isLoading.value = false\n }\n}, 250)\n\nfunction create(name) {\n model.value = { name: name.trim() }\n\n query.value = ''\n isOpen.value = false\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUSelectMenu v-model=\"model\"\n v-model:open=\"isOpen\"\n v-model:search-term=\"query\"\n :items=\"items\"\n :loading=\"isLoading\"\n label-key=\"name\"\n create-item=\"always\"\n @create=\"create\"\n @update:search-term=\"search\" />\n\u003C/template>\n```\n\n### Description\n\nI want to create new category \"Des\", but cant, because i found \"Deserts\".\nOption `create-item=\"always\"` ignored.\n\nDemonstration: https://skr.sh/vVFQ3lvSifh",[2999,3000],{"name":2905,"color":2906},{"name":2908,"color":2909},3949,"USelectMenu create-item=\"always\" not working","2025-04-23T08:22:30Z","https://github.com/nuxt/ui/issues/3949",0.69676673,{"description":3007,"labels":3008,"number":3015,"owner":2914,"repository":2915,"state":2945,"title":3016,"updated_at":3017,"url":3018,"score":3019},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v18.19.1\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@8.11.0\r\n- Builder: -\r\n- User Config: devtools, modules, tailwindcss, i18n, runtimeConfig\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @nuxt/ui@2.15.2-28557281.8d9d973, @nuxtjs/i18n@8.3.0, @vueuse/nuxt@10.9.0\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\nnpm:@nuxt/ui-edge@latest\r\n\r\n### Reproduction\r\n\r\n const coverInfoStore = useCoverInfoStore()\r\n\r\n\u003CUTextarea v-model=\"coverInfoStore.coverTitle\" />\r\n \u003CUInput v-model=\"coverInfoStore.coverTitle\" />\r\n\r\n### Description\r\n\r\nProblem:\r\nWhen using UTextarea component in conjunction with pinia and v-model, there is an inconsistency in behavior compared to using UInput.\r\n\r\nExpected Behavior:\r\nBoth UInput and UTextarea should behave consistently when used with pinia and v-model. Updates to the bound data should reflect immediately in both components.\r\n\r\nActual Behavior:\r\n\r\nWhen updating the data bound to UInput using v-model, the changes are reflected immediately in the UI.\r\nHowever, when updating the data bound to UTextarea using v-model, the changes are not reflected immediately. \r\n\r\n### Additional context\r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3009,3010,3013],{"name":2967,"color":2968},{"name":3011,"color":3012},"closed-by-bot","ededed",{"name":3014,"color":3012},"stale",1701,"Inconsistent behavior with UTextarea, pinia, and v-model compared to UInput","2025-06-19T02:12:43Z","https://github.com/nuxt/ui/issues/1701",0.6969433,["Reactive",3021],{},["Set"],["ShallowReactive",3024],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdbHBSJktU2K4UeJ3OQ37GoDS1ajqnn1iUYotbhzRaTs":-1},"/nuxt/ui/2712"]