\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```",[3189,3192],{"name":3190,"color":3191},"enhancement","a2eeef",{"name":3176,"color":3177},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.7599609,{"description":3199,"labels":3200,"number":3205,"owner":3179,"repository":3180,"state":3181,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### Package\n\nv4.x\n\n### Description\n\nI'm having trouble showing per-file validation errors when a [FileUpoad](https://ui.nuxt.com/docs/components/file-upload) component has its `multiple` prop set to `true`. \n\nBased on the [With Form validation example](https://ui.nuxt.com/docs/components/file-upload#with-form-validation) in the docs, I've wrapped the `image` schema with `z.array().min(1)` to support multi-file uploads. I would expect each file in the files slot to show the corresponding error from the validation; however, the errors aren't propagated to the UI when form validation is triggered. \n\nI created a [full example of this](https://codesandbox.io/p/devbox/condescending-forest-wxyn4p?workspaceId=ws_QLcmorLcRQZygAFv9oB7A8). \n\nThere should be default behavior to show per-file errors when there's a `schema` prop set and `multiple` is set to `true`.\n\n### Additional context\n\n_No response_",[3201,3202],{"name":3190,"color":3191},{"name":3203,"color":3204},"triage","ffffff",5146,"FileUpload: Per-file schema validation errors when multiple prop is true","2025-10-05T19:21:03Z","https://github.com/nuxt/ui/issues/5146",0.7618199,{"description":3211,"labels":3212,"number":3215,"owner":3179,"repository":3180,"state":3181,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### 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\" />",[3213,3214],{"name":3190,"color":3191},{"name":3176,"color":3177},4529,"Setting required=\"true\" on a \u003CUFormField> should also set it's child required to true","2025-07-31T14:36:21Z","https://github.com/nuxt/ui/issues/4529",0.7777804,{"description":3221,"labels":3222,"number":3225,"owner":3179,"repository":3180,"state":3226,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Description\n\nI have a file field **without** `v-model`, then I select a file. I have another field with a validation error. On submit, the validation error is shown on the email field and the file field is cleared. Is this a bug or a feature. With version `3.2.0` this behaviour does not exist. In `3.3.0` it does. It might be related to one of the dependencies though, because if I first upgrade to 3.3.0 and then go back to 3.2.0, where the lockfile still shows a lot of changes, the problem still exists.\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport type { FormError, FormSubmitEvent } from '#ui/types'\n\nconst state = reactive({\n email: undefined,\n file: undefined,\n})\n\nconst validate = (): FormError[] => {\n const errors = []\n errors.push({ name: 'email', message: 'Required' })\n return errors\n}\n\nasync function onSubmit(event: FormSubmitEvent\u003Ctypeof state>) {\n console.log(event.data)\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUForm\n :validate=\"validate\"\n :state=\"state\"\n class=\"space-y-4\"\n @submit=\"onSubmit\"\n\n \u003CUFormField label=\"Email\" name=\"email\">\n \u003CUInput v-model=\"state.email\" />\n \u003C/UFormField>\n\n \u003CUFormField label=\"File\" name=\"file\">\n \u003CUInput type=\"file\" />\n \u003C/UFormField>\n\n \u003CUButton type=\"submit\"> Submit \u003C/UButton>\n \u003C/UForm>\n\u003C/template>\n```",[3223,3224],{"name":3173,"color":3174},{"name":3176,"color":3177},4637,"closed","File field gets cleared, bug?","2025-08-21T08:42:25Z","https://github.com/nuxt/ui/issues/4637",0.731154,{"description":3232,"labels":3233,"number":3236,"owner":3179,"repository":3180,"state":3226,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### 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```",[3234,3235],{"name":3173,"color":3174},{"name":3176,"color":3177},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.74507046,{"description":3242,"labels":3243,"number":3247,"owner":3179,"repository":3180,"state":3226,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### 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",[3244,3245,3246],{"name":3190,"color":3191},{"name":3176,"color":3177},{"name":3203,"color":3204},4540,"Docs: Form validate on-submit","2025-07-22T19:11:45Z","https://github.com/nuxt/ui/issues/4540",0.75063914,{"description":3253,"labels":3254,"number":3257,"owner":3179,"repository":3180,"state":3226,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### 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",[3255,3256],{"name":3173,"color":3174},{"name":3176,"color":3177},4485,"Don't validate hidden fields.","2025-07-26T09:53:03Z","https://github.com/nuxt/ui/issues/4485",0.75117254,{"description":3263,"labels":3264,"number":3267,"owner":3179,"repository":3180,"state":3226,"title":3268,"updated_at":3269,"url":3270,"score":3271},"### 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_",[3265,3266],{"name":3190,"color":3191},{"name":3176,"color":3177},2993,"NavigationMenu with non-collapsible parents","2025-02-15T17:01:06Z","https://github.com/nuxt/ui/issues/2993",0.75940347,{"description":3273,"labels":3274,"number":3280,"owner":3179,"repository":3180,"state":3226,"title":3281,"updated_at":3282,"url":3283,"score":3284},"### 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```",[3275,3278,3279],{"name":3276,"color":3277},"bug","d73a4a",{"name":3176,"color":3177},{"name":3203,"color":3204},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,["Reactive",3286],{},["Set"],["ShallowReactive",3289],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fp6JJDy2vWgBsZ_F66eiBdABTXFxRMExuQAP9tBCgNwM":-1},"/nuxt/ui/1815"]