\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",[3018,3021,3024],{"name":3019,"color":3020},"enhancement","a2eeef",{"name":3022,"color":3023},"v3","49DCB8",{"name":3025,"color":3026},"triage","ffffff",4435,"nuxt","ui","open","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.7400953,{"description":3036,"labels":3037,"number":3041,"owner":3028,"repository":3028,"state":3030,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Describe the feature\n\nI feel as though the following feature requests should be considered for NuxtTime.\n\n- Default slot to allow for customizing how the time is displayed, while re-using the logic. For example, use with [Numberflow](https://number-flow.barvian.me/vue)\n- Additionally/Alternatively extract the logic into composable like useTime(new Date(), {...config})\n- Refresh relative time at an interval. For example, 5 mins ago would update to 6 mins ago\n- Compact appearance for relative time formatting. Example: instead of \"5 days ago\" show \"5d\"\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3038],{"name":3039,"color":3040},"pending triage","E99695",32478,"Proposing several improvements to NuxtTime","2025-06-25T20:32:32Z","https://github.com/nuxt/nuxt/issues/32478",0.746549,{"description":3047,"labels":3048,"number":3051,"owner":3028,"repository":3029,"state":3030,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Description\n\n### 🚀 Feature Request\nI’d like to suggest adding a built-in `\u003CDynamicRenderer>` component to Nuxt UI that renders dynamic, nested components based on a configuration object.\n\n### 📋 Motivation\nThis component would be ideal for:\n\n- Form builders\n\n- CMS-driven UIs\n\n- Low-code tools\n\n- Declarative UI rendering\n\nIt simplifies the process of rendering deeply nested structures without hardcoding components in the template.\n\n### 💡 Proposal\nThe DynamicRenderer would accept a config prop that defines:\n\n- The component to render\n\n- Props to bind\n\n- Slot content (including nested component trees)\n\nIt would recursively render components and their slots. Here's an example implementation:\n\n\n#### `DynamicRenderer.vue`\n```vue\n\u003Cscript setup lang=\"ts\">\ndefineProps\u003C{ config: any }>()\n\u003C/script>\n\n\u003Ctemplate>\n \u003Ccomponent :is=\"config.component\" v-bind=\"config\">\n \u003Ctemplate\n v-for=\"(slotContent, slotName) in config.slots\"\n #[slotName]\n >\n \u003Ctemplate v-if=\"typeof slotContent === 'string'\">\n {{ slotContent }}\n \u003C/template>\n\n \u003Ctemplate v-else-if=\"Array.isArray(slotContent)\">\n \u003CDynamicRenderer\n v-for=\"(nested, index) in slotContent\"\n :key=\"index\"\n :config=\"nested\"\n />\n \u003C/template>\n\n \u003Ctemplate v-else>\n \u003CDynamicRenderer :config=\"slotContent\" :key=\"slotContent.name || slotName\" />\n \u003C/template>\n \u003C/template>\n \u003C/component>\n\u003C/template>\n```\n\n\n\n#### `index.vue`\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { UButton, UCard, UContainer, UForm, UFormField, UInput } from '#components'\n\nconst config = {\n component: UContainer,\n class: 'h-screen flex justify-center items-center',\n slots: {\n default: [\n {\n component: UCard,\n slots: {\n default: [{\n component: UForm,\n class: 'space-y-4',\n slots: {\n default: [\n {\n component: UFormField,\n label: 'Username',\n name: 'username',\n required: true,\n slots: {\n default: [\n {\n component: UInput,\n placeholder: 'Enter Username',\n value: 'hh'\n }\n ]\n }\n },\n {\n component: UFormField,\n label: 'Password',\n name: 'password',\n required: true,\n slots: {\n default: [\n {\n component: UInput,\n type: 'password',\n placeholder: 'Enter Password',\n value: 'hh'\n }\n ]\n }\n },\n {\n component: UButton,\n label: 'Login',\n icon: 'i-lucide-user',\n variant: 'soft',\n type: 'submit',\n block: true\n }\n ]\n }\n }]\n }\n }\n ]\n }\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CDynamicRenderer :config=\"config\" />\n\u003C/template>\n```\n\n### Result \n\n\nIt would also be great if using this approach could eliminate the need to manually import components like:\n\n```ts\nimport { UButton, UCard, UContainer, UForm, UFormField, UInput } from '#components'\n```\n\nand instead rely on automatic resolution by the renderer itself.\n\nThanks for your work on Nuxt UI – it’s a fantastic toolkit!\n\n### Additional context\n\n_No response_",[3049,3050],{"name":3019,"color":3020},{"name":3025,"color":3026},4138,"✨ Feature Request: Add `\u003CDynamicRenderer>` component for config-driven UI rendering","2025-05-12T16:36:30Z","https://github.com/nuxt/ui/issues/4138",0.754656,{"description":3057,"labels":3058,"number":3062,"owner":3028,"repository":3029,"state":3030,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Description\n\nI want to make the text in a custom slot for a tree item child selectable.\nThe issue is that `user-select: text` doesn’t work on `\u003Cbutton>` elements in Safari (I’m using a Tauri app).\n\nIt would be great if the component allowed using a custom slot that avoids rendering a \u003Cbutton> for certain items. (Perhaps a new slot could be added to allow custom rendering?).\n\n\u003Cimg width=\"1217\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/39cf6666-e3c9-48f4-a922-90a57d604feb\" />\n\n\n### Additional context\n\n_No response_",[3059,3060,3061],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4424,"Ability to not use button container for tree custom slot","2025-06-30T07:50:57Z","https://github.com/nuxt/ui/issues/4424",0.757911,{"description":3068,"labels":3069,"number":3073,"owner":3028,"repository":3029,"state":3074,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### Description\n\nAt the moment InputNumber does not react in any way to the presence of ButtonGroup.\n\n\n\n### Additional context\n\n_No response_",[3070,3071,3072],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4155,"closed","InputNumber ButtonGroup support","2025-05-15T12:30:59Z","https://github.com/nuxt/ui/issues/4155",0.71276116,{"description":3080,"labels":3081,"number":3089,"owner":3028,"repository":3029,"state":3074,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nTo control the rows of the table, I need a slot for them. For instance, if I want to implement a reorder feature using drag and drop, I require a \u003Ctr> element to loop through.\n\n### Additional context\n\n_No response_",[3082,3083,3084,3087],{"name":3019,"color":3020},{"name":3025,"color":3026},{"name":3085,"color":3086},"closed-by-bot","ededed",{"name":3088,"color":3086},"stale",2685,"[UTable] Add the functionality to include a slot for all \u003Ctr> elements, as well as a 'default' slot.","2025-06-18T09:05:45Z","https://github.com/nuxt/ui/issues/2685",0.73296446,{"description":3095,"labels":3096,"number":3099,"owner":3028,"repository":3029,"state":3074,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Description\n\nI saw that some components (like `Modal` or `Slideover`) have the \"trigger\" fully replaceable, meanwhile others like `Select` and `SelectMenu` cannot be fully replaced. Because of that, introducing another slot to replace the entire trigger would be nice imho. But I would define it as the default slot, not a named one (like `trigger` or something else) to remain consistent with the modal/slideover one.\nThe problem is that it would introduce a breaking change, so I don't know what is the way you want to proceed.\nWhat do you think about this?\nMentioning @sandros94 as I talked about this with him on Discord.\n\n### Additional context\n\nTo have a look on this, I did some changes in a branch in my fork: \u003Chttps://github.com/nuxt/ui/compare/v3...zAlweNy26:nuxt-ui:feat/select-trigger>",[3097,3098],{"name":3019,"color":3020},{"name":3022,"color":3023},4009,"Standardize trigger slot in components","2025-05-10T17:57:56Z","https://github.com/nuxt/ui/issues/4009",0.73783,{"description":3105,"labels":3106,"number":3110,"owner":3028,"repository":3029,"state":3074,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Description\n\nDescription:\nI am currently using the UTable component from Nuxt UI and have encountered a limitation regarding the customization of table headers. Specifically, I need to create a table with multi-row headers and the ability to merge columns using colspan. For example, the multi-row spanning column headers shown in the image.However, the current implementation of the UTable component does not seem to support this feature.\n\n\nCurrent Behavior:\n\nThe header property allows for custom content using the h function, but it is limited to single-column customization.\nThe available slots are primarily designed for single-column or specific row customization and do not support multi-column header customization.\nExpected Behavior:\n\nAbility to define headers that span multiple rows and columns.\nSupport for colspan and rowspan attributes in the header configuration to allow for more complex table layouts.\nEnhanced slot functionality to support multi-column header customization.\nUse Case:\nThis feature is essential for creating complex data tables where grouped headers are necessary for better data organization and presentation. It is particularly useful in scenarios where data needs to be categorized under broader headings.\n\nProposed Solution:\n\nIntroduce a mechanism in the UTable component to allow for multi-row and multi-column header definitions.\nProvide examples and documentation on how to implement these features using the existing API or through new enhancements.\nConsider expanding the slot functionality to support more complex header customizations.\nAdditional Context:\n\nThis feature is commonly supported in other table libraries and would greatly enhance the flexibility and usability of the UTable component in Nuxt UI.\nEnvironment:\n\nNuxt UI version: [3.0.0-alpha.12]\nNuxt version: [^3.15.4]\n\nRelated Issues Link:\nhttps://github.com/nuxt/ui/issues/1289#issuecomment-2652919275\nhttps://github.com/nuxt/ui/issues/1651\nhttps://github.com/nuxt/ui/issues/2053\n\nRelated Documentation Link:\nhttps://ui3.nuxt.dev/components/table\n\n### Additional context\n\n_No response_",[3107,3108,3109],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3296,"Support for Multi-Row and Colspan Headers in UTable Component","2025-07-01T12:05:35Z","https://github.com/nuxt/ui/issues/3296",0.74044156,{"description":3116,"labels":3117,"number":3123,"owner":3028,"repository":3029,"state":3074,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Description\n\nThe PinInput component expects the v-model to be a string array. However, when the type is set to number, I think it should support an array of numbers as values too.\n\n### Additional context\n\n_No response_",[3118,3119,3120],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3121,"color":3122},"reka-ui","56d799",3751,"PinInput: v-model support Number-Array on type=number","2025-05-28T09:55:13Z","https://github.com/nuxt/ui/issues/3751",0.7455713,{"description":3129,"labels":3130,"number":3135,"owner":3028,"repository":3029,"state":3074,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### Description\n\nIt is possible add an slot named `option-append` which will be after the menu content?\r\nFor example it will be useful to add an intersection observer when creating an infinite scroll select.\n\n### Additional context\n\n_No response_",[3131,3132,3134],{"name":3019,"color":3020},{"name":3133,"color":3026},"wontfix-v2",{"name":3022,"color":3023},1167,"`USelectMenu` option-append","2025-05-23T15:24:34Z","https://github.com/nuxt/ui/issues/1167",0.7463672,["Reactive",3141],{},["Set"],["ShallowReactive",3144],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fOwLi3wOx4FmpvkIRgildWuYHnKueS7H6Ea3CbMyUoWw":-1},"/nuxt/ui/4201"]