\n\u003C/UFormGroup>\n```\n\n```\n\u003Cdiv class=“relative”>\n \u003Cinput>…\n\u003C/div>\n```\n\nHowever in version 3 it is\n\n```\n\u003CUFormField>\n \u003CUInput />\n\u003C/UFormField >\n```\n\n```\n\u003Cdiv class=“relative inline-flex items-center”>\n \u003Cinput>…\n\u003C/div>\n```\n\nThis is causing the `\u003Cinput>` to not expand to the full width of the parent container. Is there a way to edit this in Nuxt UI 3 to make it fully expand to the parent container?\n\n",[3197,3198],{"name":3146,"color":3147},{"name":3165,"color":3166},3955,"UInput not flexing when upgrading from v2 to v3","2025-04-22T14:14:04Z","https://github.com/nuxt/ui/issues/3955",0.6868425,{"description":3205,"labels":3206,"number":3209,"owner":3135,"repository":3149,"state":3150,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3207,3208],{"name":3146,"color":3147},{"name":3165,"color":3166},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.68873185,{"description":3215,"labels":3216,"number":3218,"owner":3135,"repository":3136,"state":3150,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### Environment\n\nDocs\n\n### Reproduction\n\n1. https://nuxt.com/docs/guide/directory-structure/app\r\n2. Click `nuxt.config.js` in the sidebar\r\n3. 404 error\n\n### Describe the bug\n\nDocs are incomplete, page is missing\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3217],{"name":3162,"color":3163},1393,"Docs: https://nuxt.com/docs/guide/directory-structure/nuxt.config (404 Error)","2023-10-23T12:52:00Z","https://github.com/nuxt/nuxt.com/issues/1393",0.6946139,{"description":3224,"labels":3225,"number":3228,"owner":3135,"repository":3149,"state":3150,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[3226,3227],{"name":3186,"color":3187},{"name":3165,"color":3166},3250,"Use `foo-(--bar)` instead of `foo-[var(--bar)]` for tailwindcss classes","2025-02-07T10:24:17Z","https://github.com/nuxt/ui/issues/3250",0.6949446,{"description":3234,"labels":3235,"number":3239,"owner":3135,"repository":3135,"state":3150,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.2\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ftrxnd?file=pages%2Ffetch.vue\r\n\r\n### Describe the bug\r\n\r\nWhile playing around using `useRouteQuery` composable fromVueUse library, I have noticed different behaviour watching the `ref` retrieved from `useRouteQuery` when using it with `useFetch` vs `useAsyncData`.\r\nWhenever `useAsyncData` is used to call the API and `ref` from `useRouteQuery` is listed inside `watch` array, API is being called only once whenever ref value changes. As expected.\r\nBut it is different with `useFetch`, where whenever `ref` value updates, there are two API calls made where one is cancelled by dedupe.\r\n\r\nI have prepared reproduction with two different pages, each for different implementation where behaviour can be observed.\r\nI would assume it has to do with `ref` being updated twice because URL query sync, but I am not sure why it differs.\r\n\r\nAlso I am aware of https://github.com/nuxt/nuxt/issues/24788 but trying to use vueuse implementation as of now.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3236],{"name":3237,"color":3238},"pending triage","E99695",25852,"`useAsyncData` watch vs `useFetch` watch with `useRouteQuery` ref","2025-04-02T12:46:45Z","https://github.com/nuxt/nuxt/issues/25852",0.6955149,["Reactive",3245],{},["Set"],["ShallowReactive",3248],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2Cp52Hv5oAHDJI0mKNkLoagSgUHeN3_yKABrqMwcSUY":-1},"/nuxt/ui/3235"]