` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2027,2030,2031],{"name":2028,"color":2029},"question","d876e3",{"name":1999,"color":2000},{"name":2032,"color":2033},"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.6402038,{"description":2040,"labels":2041,"number":2051,"owner":1985,"repository":2005,"state":2019,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: -\n- CLI Version: 3.23.1\n- Nitro Version: -\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nN/A\n\n### Description\n\nim trying to set the widht for a specific column, i've tried with size in the columns definition but isn't working, also i've tried with defaultColumn but still doesnt work, i need to fix the size of a specific column, is there any way to do that? \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2042,2043,2046,2047,2048],{"name":2014,"color":2015},{"name":2044,"color":2045},"needs reproduction","CB47CF",{"name":1999,"color":2000},{"name":2002,"color":2003},{"name":2049,"color":2050},"closed-by-bot","ededed",3648,"Table not working with size, minSize or maxSize in columns","2025-04-04T02:04:48Z","https://github.com/nuxt/ui/issues/3648",0.6704145,{"description":2057,"labels":2058,"number":2069,"owner":1985,"repository":1985,"state":2019,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### Environment\n\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0-rc.10-27710784.e22bbcc`\r\n- Nitro Version: `0.5.2-27709289.11cc5cd`\r\n- Package Manager: `npm@8.12.1`\r\n- Builder: `vite`\r\n- User Config: `app`, `css`, `build`, `imports`, `modules`, `nitro`, `runtimeConfig`, `typescript`, `vite`\r\n- Runtime Modules: `nuxt-graphql-client@0.1.15`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nCan't reproduce because Stacklblitz doesn't actually show any TS.\n\n### Describe the bug\n\nWhen defining a server api route, it'll autmoatically infer the right return types (yay!), so when calling `const data = $fetch('/api/test')`, `data` can be used safely.\r\n\r\nHowever if you call the API with a query parameter, `const data = $fetch('/api/test?q=hello')`, you will lose all typesafety because the returned type becomes `Promise\u003Cunknown>`.\r\n\r\nI'm not 100% sure why, but maybe because the called URL doesn't match the actual API route due to the added params?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2059,2062,2065,2066],{"name":2060,"color":2061},"types","2875C3",{"name":2063,"color":2064},"3.x","29bc7f",{"name":2014,"color":2015},{"name":2067,"color":2068},"🔨 p3-minor","FBCA04",14850,"API route types not correctly inferred when using query params in $fetch","2023-01-19T17:41:08Z","https://github.com/nuxt/nuxt/issues/14850",0.6832985,{"description":2075,"labels":2076,"number":2080,"owner":1985,"repository":2005,"state":2019,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Environment\n\nnpx nuxi info\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.10\n\n### Reproduction\n\nat local\n\n### Description\n\n\n\n\n### Additional context\n\na big error about UPopover,popover always show at wrong place\n//my component\n \u003Cdiv class=\"sys-side\">\n \u003CUPopover mode=\"hover\">\n \u003Csvgo-whatsapp>\u003C/svgo-whatsapp>\n \u003Ctemplate #content>\n \u003CPlaceholder class=\"size-48 m-4 inline-flex\" />\n \u003C/template>\n \u003C/UPopover>\n\n \u003Csvgo-email>\u003C/svgo-email>\n \u003Csvgo-wechat>\u003C/svgo-wechat>\n \u003Csvgo-phone>\u003C/svgo-phone>\n \u003C/div>\n//layout/default.vue\n \u003CHtml :lang=\"head.htmlAttrs.lang\" :dir=\"head.htmlAttrs.dir\">\n \u003CHead>\n\n\u003C!--\n \u003CTitle>{{ title }}\u003C/Title>\n-->\n \u003Ctemplate v-for=\"link in head.link\" :key=\"link.id\">\n \u003CLink :id=\"link.id\" :rel=\"link.rel\" :href=\"link.href\" :hreflang=\"link.hreflang\" />\n \u003C/template>\n \u003Ctemplate v-for=\"meta in head.meta\" :key=\"meta.id\">\n \u003CMeta :id=\"meta.id\" :property=\"meta.property\" :content=\"meta.content\" />\n \u003C/template>\n \u003C/Head>\n \u003CBody>\n \u003CUApp :toaster=\"{position:'top-center'}\">\n \u003Csys-header >\u003C/sys-header>\n \u003Csys-side>\u003C/sys-side>\n \u003Cslot />\n \u003Csys-footer>\u003C/sys-footer>\n \u003C/UApp>\n \u003C/Body>\n \u003C/Html>\n \u003C/div>\n\n\n### Logs\n\n```shell-script\n\n```",[2077,2078,2079],{"name":2014,"color":2015},{"name":2044,"color":2045},{"name":1999,"color":2000},2915,"a big error about UPopover,popover always show at wrong place","2025-01-25T13:11:46Z","https://github.com/nuxt/ui/issues/2915",0.68393385,{"description":2086,"labels":2087,"number":2090,"owner":1985,"repository":2005,"state":2019,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Description\n\nI've been trying for some time to disable the external icon as shown here but was unable to, even if target=\"_blank\":\n\u003Cimg width=\"243\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a81dfa32-a8bb-4ec7-9671-006d0161bcef\" />\n\nIn this case, I want to display the icons as below without the external icons, even if the target='_blank':\n\u003Cimg width=\"203\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d52b4a82-306b-4c69-8117-3a7e8ee6a2ea\" />\n\n\n### Additional context\n\nThe lines responsible identified here:\nhttps://github.com/nuxt/ui/blob/d4653e3c02e877eed1f8762046b2b1f001b2e84b/src/runtime/components/NavigationMenu.vue#L191\nhttps://github.com/nuxt/ui/blob/d4653e3c02e877eed1f8762046b2b1f001b2e84b/src/runtime/components/NavigationMenu.vue#L252",[2088,2089],{"name":1996,"color":1997},{"name":1999,"color":2000},2996,"Ability to disable external icon in NavigationMenu","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2996",0.68457484,{"description":2096,"labels":2097,"number":2100,"owner":1985,"repository":2005,"state":2019,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI noticed that using form validation in Nuxt UI is very simple: Add a schema to a `\u003CUForm>` component and then place `\u003CUFormGroup>`'s with the corresponding names.\n\nUnfortunately in Vue I never found a solution this simple. In fact e.g. the use of VeeValidate is very cumberstone and requires a lot of code.\n\nMight it be possible to refactor the form validation of Nuxt UI as a standalone Vue component that uses slots and provides pure functionality without styling?\n\nE.g. by providing the a \"Form\" component, that auto validated the state and providing the error messages in a reactive object, but most things are handled by the developer:\n\n```vue\n\u003CForm :schema=\"schema\" :state=\"state\" @submit=\"onSubmit\" ref=\"form\">\n \u003Clabel for=\"email\">E-Mail\u003C/label>\n \u003Cinput name=\"email\" type=\"text\" v-model=\"state.email\" />\n \u003Cdiv v-if=\"form.errors.email\">{{ form.errors.email }}\u003C/div>\n\n \u003Cbutton type=\"submit\">Submit\u003C/button>\n\u003C/Form>\n```\n\nInstead of configuring how the form validates (e.g. on each change, only after pressing submit, etc) we could use states for each value like Angular does. There the form validates on each change but each value has multiple states like is-pristine, isDirty, isUntouched and by use of those values triggering the visibility of the error messages can be precisely handled. Example:\n\n```vue\n\u003CForm :schema=\"schema\" :state=\"state\" @submit=\"onSubmit\" ref=\"form\">\n \u003Clabel for=\"email\">E-Mail\u003C/label>\n \u003Cinput name=\"email\" type=\"text\" v-model=\"state.email\" />\n \u003Cdiv v-if=\"form.errors.email && form.values.email.dirty\">{{ form.errors.email }}\u003C/div>\n\n \u003Cbutton type=\"submit\" :disabled=\"!form.isValid\">Submit\u003C/button>\n\u003C/Form>\n```",[2098,2099],{"name":1996,"color":1997},{"name":1999,"color":2000},2768,"Release form validation as standalone library","2024-12-16T09:47:15Z","https://github.com/nuxt/ui/issues/2768",0.6927779,{"description":2106,"labels":2107,"number":2113,"owner":1985,"repository":1985,"state":2019,"title":2114,"updated_at":2115,"url":2116,"score":2117},"### Describe the feature\r\n\r\nThis has been an issue for some time, so I'll do my best to explain the issue and see if we can move a fix along or consider the recommended solution below.\r\n\r\nOther relevant conversations that I was able to dig up:\r\n\r\n#15280 \r\n#22488 \r\n\r\n## Current Behavior\r\nGiven these API routes:\r\n\r\n```\r\n── api\r\n └── group\r\n ├── .get.ts\r\n ├── .post.ts\r\n └── [groupId]\r\n ├── .delete.ts\r\n ├── .get.ts\r\n └── .put.ts\r\n```\r\n\r\nThe following routes are generated in `nitro-routes.d.ts`:\r\n\r\n```ts\r\n'/api/group/': {\r\n 'get': Simplify\u003CSerialize\u003CAwaited\u003CReturnType\u003Ctypeof import('../../server/api/group/.get').default>>>>\r\n 'post': Simplify\u003CSerialize\u003CAwaited\u003CReturnType\u003Ctypeof import('../../server/api/group/.post').default>>>>\r\n }\r\n '/api/group/:groupId/': {\r\n 'delete': Simplify\u003CSerialize\u003CAwaited\u003CReturnType\u003Ctypeof import('../../server/api/group/[groupId]/.delete').default>>>>\r\n 'get': Simplify\u003CSerialize\u003CAwaited\u003CReturnType\u003Ctypeof import('../../server/api/group/[groupId]/.get').default>>>>\r\n 'put': Simplify\u003CSerialize\u003CAwaited\u003CReturnType\u003Ctypeof import('../../server/api/group/[groupId]/.put').default>>>>\r\n }\r\n```\r\n\r\n## The issue\r\n\r\nThere isn't a propper way to infer the type from the `api/group/:groupId`\r\n\r\n**Option 1: [Doesn't work]** This matches the types from `/api/group/get`\r\n```ts\r\nconst groupId = 42\r\nconst data = useFetch(`/api/group/${groupId}`)\r\n```\r\n\r\n**Option 2: [Doesn't work]**: This infers the correct types from from `/api/group/[groupId]/.get`, but the actual api call fails because we have not way to pass the _**groupID**_ value,\r\n```ts\r\nconst groupId = 42\r\nconst data = useFetch(`/api/group/:groupId/`)\r\n```\r\n\r\nThere isn't a way currently to deal with this,\r\n\r\n## Proposal\r\nThere are two way to really solve this.\r\n1. Fix the underlying type inference issue. I'm not sure if this feature is complete\r\n2. I like option 2 above because it looks pretty clean. Can we add the ability to pass parameters to the `useFetch` function that allows setting those url parameters?\r\n\r\nSomething like this:\r\n\r\n```ts\r\nconst data = useFetch('/api/group/:groupId/', {\r\n routerParams: {\r\n groupId: 42\r\n }\r\n})\r\n```\r\n\r\nThis would make the type inference work as expected, and make the API calls correctly. We already use `RouterParams` on the backend, so naming would be consistent.\r\n\r\n\r\n### Additional information\r\n\r\n- [ ] 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).",[2108,2109,2112],{"name":2063,"color":2064},{"name":2110,"color":2111},"pending triage","E99695",{"name":2044,"color":2068},26171,"Add a way to properly infer types from dynamic routes","2024-11-28T12:25:02Z","https://github.com/nuxt/nuxt/issues/26171",0.6981703,["Reactive",2119],{},["Set"],["ShallowReactive",2122],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"diGEpx_kMmqMBeol6qenZ7rdq4eXqZj-pHzr7riP0pk":-1},"/nuxt/ui/3004"]