\r\n \u003C/UDropdown>\r\n \u003C/template>\r\n\r\n \u003C/UTable>\r\n \u003C/li>`\r\n\r\nThis renders correctly and works wonderfully. The only issue is when I use the \"select\" feature, the two tables sometimes interact where they shouldn't. \r\n\r\nI see this happen when table 1 (that has 5 elements) when I select 2 elements from it, table 2 thinks all elements in table 2 have been selected. This probably has to do with a check to see if the number of selected elements match the number of elements in the table (to see if all elements are selected and change the select icon accordingly). However, when there are two separate tables, they should act independently. \r\n\r\nPicture for reference:\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nTables that are inside a list and are expected to behave independently are interacting with one another through the SELECT feature.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2945,2948],{"name":2946,"color":2947},"3.x","29bc7f",{"name":2949,"color":2950},"pending triage","E99695",25135,"closed","Table \"Select all\" gets confused when tables are inside a list","2024-01-10T14:21:12Z","https://github.com/nuxt/nuxt/issues/25135",0.73782605,{"description":2958,"labels":2959,"number":2967,"owner":2910,"repository":2911,"state":2952,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, runtimeConfig, ui\n- Runtime Modules: @nuxt/ui@3.1.0, @formkit/auto-animate/nuxt@0.8.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\n-\n\n### Description\n\nAfter upgrading from v3.0.2 to v3.1.0 I'm missing types for event binding directives and intellisense/automcomplete for attributes of all Nuxt UI components. Below I added a specific example for the Table component, but this happens to all components. I have removed node_modules, reinstalled, cleared the .nuxt and .output directories, and tried setting up a new project as well (using `npx nuxi init -t ui \u003Cmy-app>`).\n\nMissing types on event binding directives:\n\u003Cimg width=\"712\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b3bb862c-16aa-4deb-aa12-c07211034f9b\" />\n\nMissing autocomplete:\n\u003Cimg width=\"487\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8a851f0a-5894-41ae-8cdf-3f2f51d2ab52\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2960,2963,2964],{"name":2961,"color":2962},"bug","d73a4a",{"name":2907,"color":2908},{"name":2965,"color":2966},"triage","ffffff",4029,"Where are all the types? v3.0.2 -> v3.1.0 upgrade","2025-04-30T12:20:42Z","https://github.com/nuxt/ui/issues/4029",0.7454645,{"description":2973,"labels":2974,"number":2976,"owner":2910,"repository":2911,"state":2952,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.12.0\r\n- Nuxt Version: 3.10.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.5.0\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/ui@2.18.6\r\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/k6rsz6?file=%2Fapp.vue%3A1%2C1\n\n### Description\n\nI'm trying to add types for a `ref` to a `UForm` component, but when I tried to use the `setErrors` method there was the following typescript error:\r\n\r\n```\r\nProperty 'setErrors' does not exist on type\r\n'CreateComponentPublicInstanceWithMixins\u003CReadonly\u003CExtractPropTypes\u003C{ schema: { type: PropType\u003CZodSchema> | PropType\u003CYupObjectSchema\u003Cany>> | PropType\u003CJoiSchema> | PropType\u003Cany>; default: any; }; state: { type: ObjectConstructor; required: true; }; validate: { ...; }; validateOn: { ...; }; }>> & Readonly\u003C...>, ... 24 m...'.\r\nDid you mean 'errors'?\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2975],{"name":2961,"color":2962},2292,"Property 'setErrors' does not exist on type","2024-10-06T17:50:16Z","https://github.com/nuxt/ui/issues/2292",0.7547515,{"description":2982,"labels":2983,"number":2987,"owner":2910,"repository":2911,"state":2952,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2984,2985,2986],{"name":2961,"color":2962},{"name":2907,"color":2908},{"name":2965,"color":2966},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.7578636,{"description":2993,"labels":2994,"number":2997,"owner":2910,"repository":2911,"state":2952,"title":2998,"updated_at":2999,"url":3000,"score":3001},"### 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```",[2995,2996],{"name":2904,"color":2905},{"name":2907,"color":2908},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.76614887,{"description":3003,"labels":3004,"number":3011,"owner":2910,"repository":2911,"state":2952,"title":3012,"updated_at":3013,"url":3014,"score":3015},"### Description\n\nIt would be great if the Nuxt UI carousel component could support infinite scrolling, allowing users to continuously scroll through items without reaching an end. This feature is commonly seen in many modern carousels and would enhance the user experience, especially for carousels with a limited number of items or those designed for continuous looping.\n\n### Additional context\n\n_No response_",[3005,3008],{"name":3006,"color":3007},"duplicate","cfd3d7",{"name":3009,"color":3010},"enhancement","a2eeef",2286,"Add Infinite Scrolling to Nuxt UI Carousel Component","2024-10-02T09:14:42Z","https://github.com/nuxt/ui/issues/2286",0.7669026,{"description":3017,"labels":3018,"number":3024,"owner":2910,"repository":2910,"state":2952,"title":3025,"updated_at":3026,"url":3027,"score":3028},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.8.0`\r\n- Nuxt Version: `3.1.1`\r\n- Nitro Version: `2.1.0`\r\n- Package Manager: `npm@8.18.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n*\r\n\r\n### Describe the bug\r\n\r\nAfter updating from 3.0.0 to 3.1.1\r\nI'm getting errors from vue-tsc like Property 'x' does not exist on type 'AppConfig' \r\n\r\nI was trying to declare interface AppConfigInput in index.d.ts like here\r\nhttps://nuxt.com/docs/guide/directory-structure/app-config#manually-typing-app-config\r\nI also added to nuxt.config.ts\r\nexperimental: { configSchema: true, },\r\n\r\ninsideapp.config.ts I have an empty object.\r\nexport default defineAppConfig({})\r\nI'm setting appConfig dynamically based on process.env (in nuxt.config.ts), ofc it has valid types there\r\nBut it should be merged anyway.\r\n\r\n### Additional context\r\n\r\nhttps://github.com/nuxt/nuxt/pull/18410\r\n\r\n### Logs\r\n\r\n_No response_",[3019,3020,3021],{"name":2946,"color":2947},{"name":2949,"color":2950},{"name":3022,"color":3023},"needs reproduction","FBCA04",18555,"3.1.1 - Typing AppConfig stopped work after upgrade","2023-03-20T15:38:42Z","https://github.com/nuxt/nuxt/issues/18555",0.7691281,["Reactive",3030],{},["Set"],["ShallowReactive",3033],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fupnNLk7JcrtyvGbM0_6QVt7VdGz1JykzxsCkIo4WoDA":-1},"/nuxt/ui/3982"]