\n \u003C/UTooltip>\n \u003CUTooltip text=\"Delete\">\n \u003CUButton color=\"neutral\" variant=\"ghost\" size=\"xs\" icon=\"i-lucide-trash-2\" />\n \u003C/UTooltip>\n \u003CUDropdownMenu size=\"sm\" :items=\"exportItems\">\n \u003CUTooltip text=\"Export as...\">\n \u003CUButton color=\"neutral\" variant=\"ghost\" size=\"xs\" icon=\"i-lucide-file-down\" />\n \u003C/UTooltip>\n \u003C/UDropdownMenu>\n\u003C/template>\n\u003Cscript setup>\n const exportItems = [\n [\n {\n label: 'Export as...',\n type: 'label'\n },\n ],\n [\n {\n label: 'Markdown',\n onSelect () {\n \n }\n },\n {\n label: 'Plain Text',\n onSelect () {\n \n }\n },\n ]\n]\n\u003C/script>\n```\nin this case, UDropdownMenu can not work, if remove UTooltip element, it works.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2906,2909],{"name":2907,"color":2908},"bug","d73a4a",{"name":2869,"color":2870},3339,"closed","DropdownMenu cannot be nested with Tooltip components","2025-02-19T15:23:15Z","https://github.com/nuxt/ui/issues/3339",0.6889432,{"description":2917,"labels":2918,"number":2926,"owner":2872,"repository":2872,"state":2911,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Describe the feature\r\n\r\nFrom docs (https://nuxt.com/docs/guide/directory-structure/server#server-utilities):\r\n```ts\r\nimport type { EventHandler } from 'h3'\r\n\r\nexport const defineWrappedResponseHandler = (handler: EventHandler) =>\r\n defineEventHandler(async (event) => {\r\n try {\r\n // do something before the route handler\r\n const response = await handler(event)\r\n // do something after the route handler\r\n return { response }\r\n } catch (err) {\r\n // Error handling\r\n return { err }\r\n }\r\n })\r\n```\r\nFetching an endpoint with $fetch or useFetch returns wrong type\r\n```ts\r\nlet a = await $fetch(\"/api/wrappedEndpoint\")\r\n// let a: Simplify\u003CSerializeObject\u003C{\r\n// response: any;\r\n// err?: undefined;\r\n//} > | SerializeObject\u003C{\r\n// err: unknown;\r\n// response?: undefined;\r\n// }>>\r\n```\r\nSo the editor doesn't give you suggestions when you write a.something\r\n\r\nWhat about replacing it with something like this:\r\n```ts\r\nexport const defineWrappedResponseHandler = \u003CT extends EventHandlerRequest, D>(\r\n handler: EventHandler\u003CT, D>\r\n) =>\r\n defineEventHandler(async event => {\r\n try {\r\n // do something before the route handler\r\n const response = await handler(event)\r\n // do something after the route handler\r\n return { response }\r\n } catch (err) {\r\n // Error handling\r\n return { err }\r\n }\r\n })\r\n```\r\nOr at least add it below!\r\n\r\n### Additional information\r\n\r\n- [x] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2919,2920,2923],{"name":2883,"color":2884},{"name":2921,"color":2922},"types","2875C3",{"name":2924,"color":2925},"3.x","29bc7f",22967,"docs: types in the Server Utilities example not working","2023-10-15T11:13:56Z","https://github.com/nuxt/nuxt/issues/22967",0.7244778,{"description":2932,"labels":2933,"number":2937,"owner":2872,"repository":2872,"state":2911,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Describe the feature\n\nIn https://nuxt.com/docs/api/composables/use-fetch#usefetch, there are some types statically written in markdown, which are outdated (if you compare them to the types in nuxt 3.3.1). e.g. the `header` property accepts different values now.\r\n\r\nI could add a PR to fix these static types, or maybe it would be better to not include them into the docs hand-written, and refer to the file in the git? Or maybe it's possible to include the file dynamically from git?\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2934,2936],{"name":2866,"color":2935},"8DEF37",{"name":2883,"color":2884},18637,"sync types from code base into docs","2024-08-01T07:15:47Z","https://github.com/nuxt/nuxt/issues/18637",0.725996,{"description":2943,"labels":2944,"number":2951,"owner":2872,"repository":2872,"state":2911,"title":2952,"updated_at":2953,"url":2954,"score":2955},"Should we publish index.d.ts to `@types` so others can include it in their package.json dev dependencies ? \r\n\r\nhttps://github.com/nuxt/nuxt.js/blob/dev/examples/typescript/index.d.ts\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c680\">#c680\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2945,2948],{"name":2946,"color":2947},"question","cc317c",{"name":2949,"color":2950},"2.x","d4c5f9",795,"TS : Should we publish Types ? ","2023-01-18T15:39:48Z","https://github.com/nuxt/nuxt/issues/795",0.7273428,{"description":2957,"labels":2958,"number":2960,"owner":2872,"repository":2873,"state":2911,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.8.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.17.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.38\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Version\n\n^2.19.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-umrnyur4?file=app.vue\n\n### Description\n\nI am using Zod for the \u003CUForm /> validation. In the minimal reproduction, since I provided two paths for the error, the message should appear on both fields. However, the error message only shows if only 1 path is specified.\n\n### Additional context\n\n### Logs\n\n```shell-script\n\n```",[2959],{"name":2907,"color":2908},2981,"`UForm` does not show error for multiple paths","2025-01-09T14:53:06Z","https://github.com/nuxt/ui/issues/2981",0.73143774,{"description":2966,"labels":2967,"number":2970,"owner":2872,"repository":2873,"state":2911,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.9\n\n### Description\n\nSometimes, we don't want the content of the Popover to be unmounted when the popover gets closed.\nFor exemple, when building a search UI with Algolia and vue-instantsearch, i want to place refinement lists in Popovers.\nIf you apply some filters and then close the Popover, the refinement list is unmounted and the search state is lost.\n\nThis is an exemple but i think there is other cases where you don't want the content to be unmounted.\nRadix provides a forceMount prop for the Popover.Content component. \n\nWhy is this forceMount prop not available in content props for nuxt/ui ?\nIt looks like it's done on purpose so i may miss something.\n\nThank you :)\n\n### Additional context\n\n_No response_",[2968,2969],{"name":2866,"color":2867},{"name":2869,"color":2870},2804,"[v3][Popover] Allow use of forceMount","2024-12-03T12:53:01Z","https://github.com/nuxt/ui/issues/2804",0.7319271,{"description":2976,"labels":2977,"number":2984,"owner":2872,"repository":2873,"state":2911,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Description\n\nHello there! thank you all for this awesome library! I'm using the pro version to leverage the Dashboard components, which have been very useful so far, but I'm currently in need of something like this:\n\n\n\nThe idea is to have a NavBar on top of all DashboardPanels across all pages. As far as I can understand the documentation, both DashboardNavbar and DashboardToolbar can only be used inside of a DashboardPanel, but would it be possible to somehow achieve this without breaking the way that the Dashboard components interact with each other? \n\nIn version 2 I kinda went around by just nesting a DashboardPanel inside of a main one (Placed in the layout file) which the Navbar inside it, and then I placed the `\u003Cslot />` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2978,2980,2981],{"name":2946,"color":2979},"d876e3",{"name":2869,"color":2870},{"name":2982,"color":2983},"pro","5BD3CB",3627,"How to add a persistent Navbar on top of all DashboardPanels inside of a DashboardGroup?","2025-03-19T20:53:14Z","https://github.com/nuxt/ui/issues/3627",0.73254025,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fnVfW_O430FAdItuWiQDDBF1IdMiO8WOJ645Tg_wzwlE":-1},"/nuxt/ui/3655"]