\n \u003C/slot> \n```\n\n### Additional context\n\nI believe this is common throughout the library, and was wondering to post this issue or not given that there might already be a specific reason. But alas, I couldn't find one in the issues.\n\ncc, from #4411",[3050,3051,3052],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4435,"InputNumber increment/decrement button props not being passed to their respective slots","2025-07-01T17:13:20Z","https://github.com/nuxt/ui/issues/4435",0.76890796,{"description":3059,"labels":3060,"number":3064,"owner":3029,"repository":3030,"state":3065,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Description\n\nThe new CheckboxGroup component lacks the `table` variant found on the RadioGroup component. Since these components will often appear together in forms, it would be preferable to have the table variant for both of them.\n\nThis is already easily achieved with the new component by adding the RadioGroup styles to the `item` ui prop. I think it should be possible to make this change just by adding the styles to checkbox-group.ts. I'm happy to make a pull request and make the changes.\n\n### Additional context\n\n_No response_",[3061,3062,3063],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},3994,"closed","[CheckboxGroup] Add `variant=\"table\"` to match RadioGroup variants","2025-05-13T12:28:16Z","https://github.com/nuxt/ui/issues/3994",0.7104072,{"description":3071,"labels":3072,"number":3076,"owner":3029,"repository":3030,"state":3065,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Description\n\nHey guys,\nThanks to your great job :)\n\nI wanna know if has intention to add a Toggle Switch component in nuxt/ui\n\n\n\n\n\n\n### Additional context\n\n_No response_",[3073,3074,3075],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4451,"Toggle Switch","2025-07-03T01:48:56Z","https://github.com/nuxt/ui/issues/4451",0.71684426,{"description":3082,"labels":3083,"number":3087,"owner":3029,"repository":3030,"state":3065,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### 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_",[3084,3085,3086],{"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.7396373,{"description":3093,"labels":3094,"number":3102,"owner":3029,"repository":3030,"state":3065,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Description\r\n\r\nHi 👋🏻 \r\n\r\nI started using NuxtUI and realized one more thing that can be improved. Right now, For `v-model` of tabs component index (number) is used.\r\n\r\nIf we want to get the key of active tab for making API req then we have to do something like below:\r\n```ts\r\nconst activeTabKey = items[itemsModel.value]!.key\r\n\r\n// With this feature implemented we can directly use `itemsModel.value`\r\n```\r\n\r\nInstead, if we can allow using `key` then:\r\n- I'll be more readable\r\n- If we change the order of the tabs (in items array) it doesn't affect the active tab\r\n\r\n### Additional context\r\n\r\nWe can also introduce this change in v3.",[3095,3096,3097,3100],{"name":3020,"color":3021},{"name":3026,"color":3027},{"name":3098,"color":3099},"closed-by-bot","ededed",{"name":3101,"color":3099},"stale",2061,"Allow using tab item key as value for v-model","2025-06-18T09:06:22Z","https://github.com/nuxt/ui/issues/2061",0.742495,{"description":3108,"labels":3109,"number":3116,"owner":3029,"repository":3029,"state":3065,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Environment\r\n\r\n{}\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/sandbox/agitated-mendeleev-ypytew\r\n\r\n### Describe the bug\r\n\r\n`v-model` on native `\u003Cinput />` tags should not be treated as an alias of `:value`. Firstly, because it's a directive. In essence, a function. In some cases, it has the same effect as \r\n```html\r\n\u003Cinput :value=\"text\"\r\n @input=\"event => text = event.target.value />\r\n```\r\nbut not in all cases (e.g: `type`s of `'checkbox' | 'radio'`, where `v-model` can be set to a selection array and `:value` points the individual item).\r\n\r\n### Additional context\r\n\r\nThe bug can be circumvented:\r\n```html\r\n\u003Cinput\r\n v-model=\"selection\"\r\n v-bind=\"{ value: option, type }\"\r\n/>\r\n```\r\nor ignored:\r\n```html\r\n\u003Cinput\r\n v-model=\"selection\"\r\n :data-foo=\"/* ts-ignore */\"\r\n :value=\"option\"\r\n :type=\"type\"\r\n/>\r\n```\r\nbut that doesn't change the fact the type definition for `v-model` directive is wrong.\r\n___\r\nInitially encountered it on [SO](https://stackoverflow.com/questions/75452800/typescript-error-on-input-value-in-template-loop-through-object-keys-in-vue-3-n) (I'm tao in that discussion - I thought it would be a good idea if I reported the bug back to you).\r\n\r\n### Logs\r\n\r\n_No response_",[3110,3113],{"name":3111,"color":3112},"3.x","29bc7f",{"name":3114,"color":3115},"pending triage","E99695",19079,"Type definition for `v-model` directive on native input is wrong","2023-02-16T13:46:32Z","https://github.com/nuxt/nuxt/issues/19079",0.7505813,{"description":3122,"labels":3123,"number":3127,"owner":3029,"repository":3030,"state":3065,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Description\n\nAs the title says, I think it would be nice to introduce a prop named `square` (like the one for the `Button` component) to be able to have a squared badge for those times where you have only the `icon` and not a label.\n\nCan I get this assigned? I would like to open a PR about this :)\n\n### Additional context\n\n_No response_",[3124,3125,3126],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4006,"[Badge] introduce prop `square`","2025-05-13T12:44:24Z","https://github.com/nuxt/ui/issues/4006",0.7517621,{"description":3133,"labels":3134,"number":3139,"owner":3029,"repository":3030,"state":3065,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nI have a use case where I'd like this value to be `false`. Would it be possible to make this configurable?\n\n### Additional context\n\nhttps://github.com/nuxt/ui/blob/dev/src/runtime/components/navigation/CommandPalette.vue#L30",[3135,3136,3137,3138],{"name":3020,"color":3021},{"name":3026,"color":3027},{"name":3098,"color":3099},{"name":3101,"color":3099},2710,"[CommandPalette] Make the `hold` prop of ComboboxOptions configurable","2025-06-18T09:05:43Z","https://github.com/nuxt/ui/issues/2710",0.7524807,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fcRzgA1MXzY02mTSEnS0ywXu0MJguh0TeGuONhpAI7j4":-1},"/nuxt/ui/4246"]