\n \u003C/template>\n \u003Ctemplate #increment>\n \u003CUButton\n :loading=\"loadingInc\"\n variant=\"link\"\n icon=\"i-lucide-plus\"\n @click=\"loadingInc = true\"\n :ui=\"{\n base: 'text-gray-500 hover:text-[var(--ui-color-primary-500)] disabled:text-gray-500 cursor-pointer',\n }\"\n />\n \u003C/template>\n \u003C/UInputNumber>\n````\n\nbest,\ngregor\n\n### Additional context\n\n_No response_",[3168,3169],{"name":3138,"color":3139},{"name":3141,"color":3142},3159,"closed","option to disable on press behaviour for increment/decrement for inputNumber component","2025-05-14T15:41:35Z","https://github.com/nuxt/ui/issues/3159",0.6690139,{"description":3177,"labels":3178,"number":3182,"owner":3147,"repository":3148,"state":3171,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### 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_",[3179,3180,3181],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4155,"InputNumber ButtonGroup support","2025-05-15T12:30:59Z","https://github.com/nuxt/ui/issues/4155",0.6801854,{"description":3188,"labels":3189,"number":3192,"owner":3147,"repository":3148,"state":3171,"title":3193,"updated_at":3194,"url":3195,"score":3196},"### Description\n\nIn InputNumber, the props used for the Increment and Decrement button are not passed to their slots, this causes difficulty in attempting to access those props in the case functionality needs to be added/overridden, but aesthetics (or ARIA) want to be maintained.\n\nThe increment button is an example of this, whereby `incrementIcon`, `color`, `size`, the translation, and the v-bind props for the button aren't passed to the slot. Thus, to access them again, code needs to be duplicated in order to recompute these properties, and defeats the purpose of DRY code. https://github.com/nuxt/ui/blob/f761369888c49fd0ee0f028dcf3c55dd5fbd2cae/src/runtime/components/InputNumber.vue#L176-L185\n\nA possible, simple solution might look like this (using scoped slots):\n```vue\n \u003Cslot name=\"increment\" :icon=\"incrementIcon\" :color=\"color\" :size=\"size\" :aria-label=\"t('inputNumber.increment')\" variant=\"link\" :bind=\"typeof increment === 'object' ? increment : undefined\"> \n \u003CUButton \n :icon=\"incrementIcon\" \n :color=\"color\" \n :size=\"size\" \n variant=\"link\" \n :aria-label=\"t('inputNumber.increment')\" \n v-bind=\"typeof increment === 'object' ? increment : undefined\" \n /> \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",[3190,3191],{"name":3138,"color":3139},{"name":3141,"color":3142},4435,"InputNumber increment/decrement button props not being passed to their respective slots","2025-08-17T13:50:25Z","https://github.com/nuxt/ui/issues/4435",0.69705784,{"description":3198,"labels":3199,"number":3203,"owner":3147,"repository":3148,"state":3171,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### Description\n\nIt would be cool if input number could have a button that can be shown beside either the increment/decrement button which, upon clicking it, resets the input back to its default value.\n\nThis is useful in forms whereby there may already be a sensibly inferred default for a value, but I want to allow the user to override that value without \"getting in the way\", and then if they want to change that value back to its default, the press of this reset button will reset the input back to its predefined default.\n\nAs of right now, I've used on a form field's label slot, a checkbox, that when toggled, enables my input and lets the user override the value, but this requires a click of the toggle, and then incrementing/decrementing the value.\nBut I'd prefer my UI to adapt to the user's needs on the fly, so say they want to change the value, they press the increment/decrement buttons, the input number's border changes to an active color like primary through the `highlight` option, thus indicating a change/override. **Where this comes in useful,** is once the user wants to revert the value back to default, the revert button in one click would revert the input's border back to the default secondary color (with `highlight` set to false) and the value displayed would revert to the default.\n\nThe reason for opening this PR is that I've tried implementing this using the `increment` slot in InputNumber, but I found myself having to copy a lot of the logic from InputNumber just to replicate the increment button, to then have my custom reset button and to get the Reka UI NumberFieldIncrement to pass the props to the right button, and it was starting to get clunky, so I thought about opening this issue to discuss this implementation here.\n\n### Additional context\n\nI'll attach some media tomorrow showing what I mean.",[3200,3201,3202],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4411,"Button to reset input number to default value","2025-06-30T06:06:01Z","https://github.com/nuxt/ui/issues/4411",0.69773805,{"description":3209,"labels":3210,"number":3214,"owner":3147,"repository":3148,"state":3171,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Description\n\nCurrently, this component is somewhat misleading. Its name clearly states that it is a group for buttons. However, if you go inside, you will find examples not only with buttons, but also with input and badge.\n\nI suggest renaming the component to `Group` so that people don't get confused and use it everywhere.\n\n### Additional context\n\n_No response_",[3211,3212],{"name":3138,"color":3139},{"name":3213,"color":3142},"v4",4544,"Rename `ButtonGroup` to `FieldGroup`","2025-08-13T12:11:48Z","https://github.com/nuxt/ui/issues/4544",0.73623437,{"description":3220,"labels":3221,"number":3227,"owner":3147,"repository":3148,"state":3171,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Description\n\nWhen adding input tags, it would be awesome to have the ability to run logic that has the ability to stop the tag from being added\n\n### Additional context\n\n_No response_",[3222,3223,3224],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3225,"color":3226},"upstream","78bddb",4406,"Validation Logic","2025-07-12T12:38:24Z","https://github.com/nuxt/ui/issues/4406",0.739044,{"description":3233,"labels":3234,"number":3238,"owner":3147,"repository":3148,"state":3171,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### 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_",[3235,3236,3237],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4006,"[Badge] introduce prop `square`","2025-05-13T12:44:24Z","https://github.com/nuxt/ui/issues/4006",0.7566341,{"labels":3244,"number":3254,"owner":3147,"repository":3147,"state":3171,"title":3255,"updated_at":3256,"url":3257,"score":3258},[3245,3248,3251],{"name":3246,"color":3247},"3.x","29bc7f",{"name":3249,"color":3250},"components","05B979",{"name":3252,"color":3253},"🔨 p3-minor","FBCA04",13498,"Cant find components that have numbers in its name (only on dash case)","2023-01-19T16:58:01Z","https://github.com/nuxt/nuxt/issues/13498",0.75681967,["Reactive",3260],{},["Set"],["ShallowReactive",3263],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fnT2PcmP6zrIJOv5B5F1B4mtnzFShHBE53pZV3zQF0Jc":-1},"/nuxt/ui/4718"]