\n\n\n### Description\n\nIn Nuxt UI v3, the \u003CUTable /> component does not provide any trigger event when clicking on a table row. In contrast, the v2 version included the @select event, which allowed developers to handle row clicks effectively. This regression impacts the ability to implement common interaction patterns, such as handling row selection or performing actions based on user clicks.\n\nDoes Nuxt UI v3 have an event similar to the @select event from v2 for the \u003CUTable /> component? Specifically, is there a way to trigger an event when a table row is clicked?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3034,3037],{"name":3035,"color":3036},"bug","d73a4a",{"name":3038,"color":3039},"v3","49DCB8",3010,"ui","closed","UTable row click event UI3","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3010",0.7577441,{"description":3048,"labels":3049,"number":3053,"owner":3024,"repository":3024,"state":3042,"title":3054,"updated_at":3055,"url":3056,"score":3057},"E.g: \r\n\r\nThis common problem can avoid many `Issues`\r\n\r\nWhat do y'all think :)",[3050],{"name":3051,"color":3052},"discussion","538de2",14689,"Add FAQ section to the docs for common issues","2025-06-06T09:01:11Z","https://github.com/nuxt/nuxt/issues/14689",0.7624125,{"description":3059,"labels":3060,"number":3065,"owner":3024,"repository":3041,"state":3042,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nWith the addition of the ColorPicker component, it would be a nice addition to allow Nuxt UI colors (like primary, secondary, error, etc..) to read from, and apply, user-input colors.\n\nIt's worth noting that admittedly, it's a little less more low priority given the extensive list of predefined colors.\n\n### Additional context\n\n_No response_",[3061,3064],{"name":3062,"color":3063},"enhancement","a2eeef",{"name":3038,"color":3039},2849,"Runtime custom color support for Nuxt UI colors","2024-12-10T09:30:23Z","https://github.com/nuxt/ui/issues/2849",0.77174425,{"description":3071,"labels":3072,"number":3076,"owner":3024,"repository":3024,"state":3042,"title":3077,"updated_at":3078,"url":3079,"score":3080},"Similar like the folks @nodejs have done (https://github.com/nodejs/help), I think we could benefit if all the help related issues on _how to use_ nuxt (or one of its components) would be moved to a separate repo. Maybe even under @nuxt-community so more people can help, clean and resolve issues. But keep this tracker for bugs and features only.\r\n\r\nAlthough the nuxt-trinity :angel: tries to keep the tracker as clean as possible, I still find it quite confusing by time. If you look at the current first page there are only 4 bug/feature issues, the other 21 are all general help related.\r\nTake the memory leak issue currently in `rc11` as an example, there are two duplicate open issues about that (1695 and 1728), but they only appear on page __3__. I was surprised when yesterday 1984 appeared in which it was mentioned that the bug was (probably) solved already, while that is a great thing unfortunately nothing about that seems to be mentioned in the open issues 1695 or 1728. Probably that's partially caused because its just difficult now to keep track of all the bug issues?\r\n\r\nSplitting the help wanted issues into a separate repo should keep this issue tracker much cleaner so its easier:\r\n- for the nuxt-trinity to keep us informed about bug/feature statuses / progress\r\n- and for us users/developers to check if our issue has already been reported or not\r\n\r\nProbably we would need to add an `ISSUE_TEMPLATE` that explains this.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1770\">#c1770\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3073],{"name":3074,"color":3075},"2.x","d4c5f9",1995,"(proposal) Use this tracker for bugs/features only, move 'help wanted' to separate repo","2023-01-18T15:42:55Z","https://github.com/nuxt/nuxt/issues/1995",0.7737486,{"description":3082,"labels":3083,"number":3088,"owner":3024,"repository":3041,"state":3042,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nAccording to the documentation for using slots, we should use the following:\n\n```\n\u003Ctemplate #name-cell=\"{ row }\">\n \u003Cdiv class=\"flex items-center gap-3\">\n {{ row.original.position }}\n \u003C/div>\n\u003C/template>\n\n```\nThe `row.original` object provides access to the row data. However, in previous versions, we could also access the table index like this:\n\n`#name-cell=\"{ row, index }\"\n`\n\nThis allowed us to display a numeric sequence for the table data. With the latest version, is there a way to access an index within the table?\n",[3084,3087],{"name":3085,"color":3086},"question","d876e3",{"name":3038,"color":3039},2729,"How Can I Get the Index When Using Slots in a Table?","2024-11-22T18:49:16Z","https://github.com/nuxt/ui/issues/2729",0.7776809,{"description":3094,"labels":3095,"number":3104,"owner":3024,"repository":3041,"state":3042,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.18.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, modules\n- Runtime Modules: @nuxt/ui@3.0.1, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0\n- Build Modules: -\n- Typescript: 5.8.2\n- Vue-tsc: 2.2.8\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\n```\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n/>\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```",[3096,3097,3098,3101],{"name":3035,"color":3036},{"name":3038,"color":3039},{"name":3099,"color":3100},"typescript","3A629E",{"name":3102,"color":3103},"triage","ffffff",3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.77830744,{"labels":3110,"number":3114,"owner":3024,"repository":3024,"state":3042,"title":3115,"updated_at":3116,"url":3117,"score":3118},[3111,3113],{"name":3062,"color":3112},"8DEF37",{"name":3074,"color":3075},9107,"Tu","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9107",0.7785077,{"description":3120,"labels":3121,"number":3128,"owner":3024,"repository":3129,"state":3042,"title":3130,"updated_at":3131,"url":3132,"score":3133},"_Improve the design of the modules page with [Raycast](https://www.raycast.com/store) page as the main source of inspiration._\n\n### Todos\n- [ ] Create a responsive design for the modules listing page sync with the API.\n- [ ] Card are external links.\n",[3122,3125],{"name":3123,"color":3124},"design","00bd6f",{"name":3126,"color":3127},"dev","018415",1337,"nuxt.com","Modules Page","2023-10-10T14:44:51Z","https://github.com/nuxt/nuxt.com/issues/1337",0.7791356,{"description":3135,"labels":3136,"number":3139,"owner":3024,"repository":3024,"state":3042,"title":3140,"updated_at":3116,"url":3141,"score":3142},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚 -->\n\n### Is your feature request related to a problem? Please describe.\n\n\u003C!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\n\n### Describe the solution you'd like\n\n\u003C!-- A clear and concise description of what you want to happen. Adding some code examples would be neat! -->\n\n### Describe alternatives you've considered\n\n\u003C!-- A clear and concise description of any alternative solutions or features you've considered. -->\n\n### Additional context\n\n\u003C!-- Add any other context or screenshots about the feature request here. -->\n",[3137,3138],{"name":3062,"color":3112},{"name":3074,"color":3075},9083,"Hi","https://github.com/nuxt/nuxt/issues/9083",0.7801405,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fn_QZ3CB66DAXwP7tFnjrCIQlnGOk1SEIICvXAKA4Kaw":-1},"/nuxt/test-utils/908"]