\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[3036,3039],{"name":3037,"color":3038},"enhancement","a2eeef",{"name":3023,"color":3024},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.7599609,{"description":3046,"labels":3047,"number":3053,"owner":3026,"repository":3027,"state":3028,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Description\n\nWhile using NuxtUI (which is awesome btw \u003C3 ) , I understood that you can set the `\"required\"` prop to any form element on itself directly without using it in a `\u003CUFormField>`. And that's great because you don't always need a label or you can set it as required without having the asterisk on it's label.\n\nBut I think that when you set `\"required\"` **directly** on the `\u003CUFormField>`, it's child should be required too (and having `\"required\" `in the DOM too) as I don't see any reason it shouldn't ; and also it's repetitve to set it to both components. Correct me if I am missing something or if there's a reason for it !\n\n\n### Additional context\n\n[Here is an example on the NuxtUI website ](https://ui.nuxt.com/components/form-field#label) where a \u003CUFormField> is required but it's \u003CUInput> child is not set required in the DOM :\n\u003Cimg width=\"779\" height=\"298\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5d37f843-b915-4e9e-af08-ee662244388f\" />\nThe input rendered in the DOM :\n\u003Cimg width=\"428\" height=\"128\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3be31e65-187f-48cb-8ea5-b5a1cb7286dc\" />",[3048,3049,3050],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3051,"color":3052},"triage","ffffff",4529,"Setting required=\"true\" on a \u003CUFormField> should also set it's child required to true","2025-07-15T12:21:20Z","https://github.com/nuxt/ui/issues/4529",0.7777804,{"description":3059,"labels":3060,"number":3063,"owner":3026,"repository":3027,"state":3064,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### 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```",[3061,3062],{"name":3020,"color":3021},{"name":3023,"color":3024},3294,"closed","UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.74507046,{"description":3070,"labels":3071,"number":3075,"owner":3026,"repository":3027,"state":3064,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Description\n\nIn v2 there was the option to validate a form only when submitting:\n\n```html\n\u003CUForm\n :schema\n :state\n :validate-on=\"['submit']\"\n>\n```\n\nWith v3 this option is gone. Can it be brought back?\n\n### Additional context\n\nI once read that form validation / show errors on submit and on blur are the best user experiences (depending on usecase) but the first one isnt possible anymore?\n\nRelated: https://github.com/nuxt/ui/issues/3853",[3072,3073,3074],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3051,"color":3052},4540,"Docs: Form validate on-submit","2025-07-22T19:11:45Z","https://github.com/nuxt/ui/issues/4540",0.75063914,{"description":3081,"labels":3082,"number":3085,"owner":3026,"repository":3027,"state":3064,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Description\n\nI am implementing skip logic in my form. Certain questions can be visible or hidden depending upon other questions answers. But zod is validating those hidden questions even. Is there a way to stop that",[3083,3084],{"name":3020,"color":3021},{"name":3023,"color":3024},4485,"Don't validate hidden fields.","2025-07-26T09:53:03Z","https://github.com/nuxt/ui/issues/4485",0.75117254,{"description":3091,"labels":3092,"number":3095,"owner":3026,"repository":3027,"state":3064,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Description\n\nUsing [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu) parent items are currently always collapsible. The following is not possible:\n\n\u003Cimg width=\"252\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/21c6d595-d24d-47c8-bdb5-064a7582f5ec\" />\n\nIt would be an amazing to have a new prop `collapsible: boolean`. If set to true the parent is not clickable and the children are always visible.\n\n### Additional context\n\n_No response_",[3093,3094],{"name":3037,"color":3038},{"name":3023,"color":3024},2993,"NavigationMenu with non-collapsible parents","2025-02-15T17:01:06Z","https://github.com/nuxt/ui/issues/2993",0.75940347,{"description":3101,"labels":3102,"number":3108,"owner":3026,"repository":3027,"state":3064,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.13.1\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: telemetry, ssr, future, compatibilityDate, modules, hooks, nitro, css, routeRules, devtools, experimental, typescript, imports\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @vueuse/nuxt@13.3.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/suspicious-water-smppjv\n\n### Description\n\nThe docs note that you can access exposed variables from `UForm`. I've found that the following fields are not reactive:\n- dirty \n- dirtyFields\n- blurredFields\n- touchedFields\n\n### Additional context\n\nI see in the [source](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue) that they're not defined with `ref` or `reactive`.\n\nAdditionally, the `dirty` computed that gets exposed would never get updated since `dirtyFields` is not reactive.\n\n### Logs\n\n```shell-script\n\n```",[3103,3106,3107],{"name":3104,"color":3105},"bug","d73a4a",{"name":3023,"color":3024},{"name":3051,"color":3052},4238,"Form exposed dirty, dirtyFields, blurredFields, and touchedFields are not reactive","2025-06-24T15:56:14Z","https://github.com/nuxt/ui/issues/4238",0.76058745,{"description":3114,"labels":3115,"number":3120,"owner":3026,"repository":3027,"state":3064,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Environment\n\nJust reporting an issue on the nuxt docs site. \n\n### Version\n\nhttps://ui.nuxt.com/components/button\n\n### Reproduction\n\nGo on to the nuxt website, this section in particular: \n\nhttps://ui.nuxt.com/components/button#icon\n \nand click 'trailing'. this should reproduce the issue. \n\n\n### Description\n\nWhen on the live docs site, on the button page, clicking 'trailing' docs this happens: \n\n\n\nThe page is: \n\nhttps://ui.nuxt.com/components/button#icon\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3116,3117],{"name":3104,"color":3105},{"name":3118,"color":3119},"documentation","0075ca",2425,"Bug on live docs site","2024-10-21T10:20:07Z","https://github.com/nuxt/ui/issues/2425",0.7618403,{"description":3126,"labels":3127,"number":3131,"owner":3026,"repository":3027,"state":3064,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### Description\n\nIn my opinion, the methods `setErrors`, `getErrors`, and `clear` of the Form component should filter using `.startsWith` on the error name. I suggest this because it would be helpful to clear all subpaths of a nested object or array.\n\nTo avoid introducing \"breaking changes,\" perhaps we could add an `exact` argument to these methods (defaulting to true). When `exact` is true, they operate as they currently do; when false, they utilise `startsWith`. \n\nI am happy to submit a PR for this if everyone agrees with the idea.\n\n### Additional context\n\n_No response_",[3128,3129,3130],{"name":3037,"color":3038},{"name":3023,"color":3024},{"name":3051,"color":3052},4524,"Better form errors path handling","2025-07-28T13:23:21Z","https://github.com/nuxt/ui/issues/4524",0.7661665,["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fp6JJDy2vWgBsZ_F66eiBdABTXFxRMExuQAP9tBCgNwM":-1},"/nuxt/ui/1815"]