`\n\nit doesn't work that way\n\nI really ask for help!",[2019,2022],{"name":2020,"color":2021},"question","d876e3",{"name":1988,"color":1989},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.6918014,{"description":2029,"labels":2030,"number":2034,"owner":1991,"repository":1992,"state":1993,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@11.2.0\n- Builder: -\n- User Config: compatibilityDate, devtools, nitro, css, modules, vite\n- Runtime Modules: @nuxt/fonts@0.11.0, @nuxt/content@3.4.0, @nuxt/icon@1.11.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.5, @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex flex-col items-center justify-center gap-4 h-screen\">\n\n {{ state }}\n\n \u003Cdiv class=\"flex items-center gap-2\">\n \u003CUTree\n :items=\"gates\"\n label-key=\"label\"\n value-key=\"id\"\n v-model=\"state.gate\" \n >\n \u003C/UTree>\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n\n\n\u003Cscript\n lang=\"ts\"\n setup\n>\n\nimport type { FormSubmitEvent } from '@nuxt/ui'\n\ninterface Gate {\n id: number,\n label: string,\n uname: string\n}\n\ntype Schema = {\n gate: Gate\n}\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n gate: undefined,\n})\n\nconst gates = [{id:0, uname: null, label: \"unknown\"}, {id:1, uname: \"first-gate\", label: \"First\"}]\n\n\u003C/script>\n```\n\n### Description\n\nvalue-key points to id or missed.\n\nv-model type check points to id:number but there is full object.\n\n\n\n### Additional context\n\nHow to get full object here when bug fixed?\n\n### Logs\n\n```shell-script\n\n```",[2031,2032,2033],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2009,"color":2010},3762,"UTree value-key not working","2025-04-01T09:12:02Z","https://github.com/nuxt/ui/issues/3762",0.694055,{"description":2040,"labels":2041,"number":2045,"owner":1991,"repository":1992,"state":2046,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[2042],{"name":2043,"color":2044},"enhancement","a2eeef",2398,"closed","Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.657034,{"description":2052,"labels":2053,"number":2054,"owner":1991,"repository":2055,"state":2046,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### 📚 Description\r\n\r\nI got a 404 error when I accessed the **learn more** link on the [cloudflare](https://nuxt.com/deploy/cloudflare) page.\r\nI investigated the cause and found that the URL path was incorrect.",[],1520,"nuxt.com","bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.6728622,{"description":2061,"labels":2062,"number":2066,"owner":1991,"repository":1991,"state":2046,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.8.1\r\n- Builder: -\r\n- User Config: srcDir, components, devtools, modules, vite, hooks, app, runtimeConfig\r\n- Runtime Modules: @vueuse/nuxt@10.11.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-vxspid?file=src%2Fplugins%2FclickOutside.ts\n\n### Describe the bug\n\nHello, not sure if you can help with this. I'm trying to implement a basic click outside functionality in a nuxt app.\r\nI'm trying to use @vueuse/components and I import @vueuse/nuxt in modules in nuxt config.\r\nmodules: [\r\n '@vueuse/nuxt',\r\n ],\r\n Then I create a plugin with this\r\n \r\n import { vOnClickOutside } from '@vueuse/components'\r\n\r\nexport default defineNuxtPlugin((nuxtApp) => {\r\n nuxtApp.vueApp.directive('clickOutside', vOnClickOutside)\r\n})\r\n\r\nHowever, I keep receiving this message after trying to use the dom element \u003COnClickOutside> in the HTML of the page :\r\n\r\n[Vue warn]: Failed to resolve component: OnClickOutside \r\nIf this is a native custom element, make sure to exclude it from \r\ncomponent resolution via compilerOptions.isCustomElement.\r\n\r\nIf I try to use the v-on-click-outside directive in the HTML I receive the following error : \r\n\r\n[Vue warn]: Failed to resolve directive: on-click-outside\r\n\r\nI don't know which would be a correct solution for this.\r\n\r\nThank you in advance for your help\r\n\r\nCarlota\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2063],{"name":2064,"color":2065},"pending triage","E99695",28060,"@vueuse/nuxt + @vueuse/components => vOnClickOutside","2024-07-05T22:04:25Z","https://github.com/nuxt/nuxt/issues/28060",0.68091446,{"description":2072,"labels":2073,"number":2076,"owner":1991,"repository":1992,"state":2046,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Description\n\nHi,\n\nhere in the first form in nuxtui2\nhttps://ui.nuxt.com/components/form \nthe behaviour is that the input field is validated after the blur. If there is an error and I correct it, the error is fixed immediately.\n\nIn v3 the behaviour is different. I have seen the prop validateOn so I can change it to blur, but not like first onBlur and then onInput like in v2.\n\nbest,\ngregor",[2074,2075],{"name":2002,"color":2003},{"name":1988,"color":1989},3006,"How can I get the same form validation behaviour as in v2?","2025-01-06T17:48:11Z","https://github.com/nuxt/ui/issues/3006",0.6828127,{"description":2082,"labels":2083,"number":2084,"owner":1991,"repository":2085,"state":2046,"title":2086,"updated_at":2087,"url":2088,"score":2089},"Hello everyone,\r\n\r\nI have a few questions about Nuxt test-utils.\r\n\r\nMy situation:\r\n\r\n- I have a Vue.js project with Vue test-utils;\r\n- I have a Nuxt.js project where I would like to add testing;\r\n\r\nI'm looking into different options for libraries to test my Nuxt.js project. Ideally, I would like to have something very similar to Vue test-utils, in order to avoid headaches when working on both projects. Nuxt test-utils seems like an interesting option, but I was wondering what are its advantages compared to just using Vue test-utils? Thanks!",[],451,"test-utils","Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/451",0.6868609,{"description":2091,"labels":2092,"number":2095,"owner":1991,"repository":1992,"state":2046,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### Description\n\nsame as https://ui.nuxt.com/getting-started/installation#edge and https://ui.nuxt.com/pro/getting-started/installation#edge to test new components before release \n\n### Additional context\n\n_No response_",[2093,2094],{"name":2043,"color":2044},{"name":1988,"color":1989},2962,"Create a edge version for `@nuxt/ui` and `@nuxt/ui-pro` v3","2025-01-25T13:12:16Z","https://github.com/nuxt/ui/issues/2962",0.6919151,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"BPsGVzvQcaPPCAPgzAznT-mSgCD9_J-K7dUSKeInLdk":-1},"/nuxt/ui/3522"]