\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n :value-key=\"undefined\"\n/>\n// will work but i need to handle label display manually using slot\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n/>\n```\n\n### Description\n\nI'm currently migrate my project to NuxtUi V3 and I have some issues with `\u003CUInputMenu />` and `\u003CUSelectMenu />`. On my selects I want to retrieve the full object selected so I don't set `value-key` but for display purpose I use the `label-key` props, however when I do this I get this typescript error on the `v-model` :\n```\nUnable to assign type 'User | undefined' to type 'string | undefined'.\nUnable to assign type 'User' to type 'string'. ts-plugin(2322)\n```\nAfter some research, I think the `label-key` alter the `value-key` type and that's what triggers the error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3068,3071,3072,3075],{"name":3069,"color":3070},"bug","d73a4a",{"name":3044,"color":3045},{"name":3073,"color":3074},"typescript","3A629E",{"name":3058,"color":3059},3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.6982858,{"description":3082,"labels":3083,"number":3091,"owner":3020,"repository":3047,"state":3032,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[3084,3087,3088],{"name":3085,"color":3086},"question","d876e3",{"name":3044,"color":3045},{"name":3089,"color":3090},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.69987315,{"description":3097,"labels":3098,"number":3099,"owner":3020,"repository":3100,"state":3032,"title":3101,"updated_at":3102,"url":3103,"score":3104},"My folder structure looks the same as it is described in the documentation (https://nuxt.com/modules/icon#custom-local-collections):\n\n`assets/my-icons/photogrammetry.svg`\n\nHowever, I load content from a json file:\n\n```json\n{\n \"data\": {\n \"0\": {\n \"title\": \"Video- & Photography\",\n \"icon\": \"my-icon:photogrammetry\",\n \"iconColor\": \"text-cyan-400\",\n [...]\n },\n```\n\n... into the component:\n\n```vue\n\u003Cscript setup>\nimport services from \"/public/jsons/services.json\"\n...\n\u003C/script>\n\n\u003Ctemplate>\n[...]\n \u003Cdiv class=\"[ card ] absolute\" :class=\"service.iconColor\">\n \u003CIcon :name=\"service.icon\" :color=\"service.iconColor\" size=\"10rem\" />\n \u003C/div>\n[...]\n\u003C/template>\n```\n\nThe icon (which is and remains black) does not accept any color, while any standard implementation (icon from a downloaded icon set like mdi) does indeed change the color of an icon.\n\n(Just in case this is not an error: What kind of \"treatment\" do I have to apply to make my icon accept color?)",[],307,"icon","custom local collections do not accept props like color","2024-11-23T10:19:42Z","https://github.com/nuxt/icon/issues/307",0.7048978,{"description":3106,"labels":3107,"number":3110,"owner":3020,"repository":3047,"state":3032,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI would like to keep the behavior of the popover opening only on click, but also allow it to close when something in the content slot is clicked.\n\nSuggestion:\n``` \u003CUPopover :content=\"{align: 'start'}\">\n \u003Ctemplate #default=\"{open}\">\n ....\n \u003C/template>\n \u003Ctemplate #content=\"{close}\">\n \u003Cdiv class=\"p-2\">\n \u003Cul class=\"flex flex-col gap-1 min-w-[150px]\">\n \u003Cli v-for=\"assistant in assistantsList\"\n :key=\"assistant.documentUuid\"\n @click=\"assistantSelected = assistant; close()\"\n class=\"p-1 rounded-md bg-neutral-800/40 hover:bg-neutral-800 cursor-pointer\">\n \u003Cp class=\"text-sm\">{{ assistant.name }}\u003C/p>\n \u003C/li>\n \u003C/ul>\n \u003C/div>\n \u003C/template>\n \u003C/UPopover>```\n\n### Additional context\n\n_No response_",[3108,3109],{"name":3041,"color":3042},{"name":3044,"color":3045},2789,"[v3][Popover] Close method exposed to the `content` slot","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2789",0.7087469,{"description":3116,"labels":3117,"number":3123,"owner":3020,"repository":3020,"state":3032,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### What problem does this feature solve?\n\nI have markdown files that I would like as pages. I can add a loader that compiles `.md` files to Vue components, but adding a `page.md` file in the `pages` directory doesn't seem to get registered as a page.\n\n### What does the proposed changes look like?\n\nAgnostic file type/extension for pages as long as there's a loader that can compile it into a Vue component.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c7151\">#c7151\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3118,3120],{"name":3041,"color":3119},"8DEF37",{"name":3121,"color":3122},"2.x","d4c5f9",3378,"Various file types for Pages","2023-01-22T15:50:41Z","https://github.com/nuxt/nuxt/issues/3378",0.71088374,{"description":3129,"labels":3130,"number":3135,"owner":3020,"repository":3047,"state":3032,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\nv2.18.7\n\n### Reproduction\n\n-\n\n### Description\n\nThis outputs two unnecessary `::` at the end. Looks like something is going wrong with the collapsible. Also when I add other fields after the collapsible, it breaks as well.\n\n```markdown\n::field-group\n::field{name=\"fallback_image\" type=\"string\"}\n::collapsible{name=\"options\"}\n\ntest\n\n::\n::\n::\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3131,3132],{"name":3069,"color":3070},{"name":3133,"color":3134},"pro","5BD3CB",2426,"Weird collapsible formatting in field-group","2024-11-19T15:20:24Z","https://github.com/nuxt/ui/issues/2426",0.7125749,["Reactive",3141],{},["Set"],["ShallowReactive",3144],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fd_B7_iTxRbPrIqD3c6qt2HXmJqM2L_pyVvAeFL_DG1Y":-1},"/nuxt/ui/3371"]