\r\n \u003CNuxtLink to=\"/a/id\">Link to A + param\u003C/NuxtLink>\r\n \u003C/div>\r\n\r\n \u003Cdiv>\r\n \u003CNuxtLink to=\"/b\">Link to B\u003C/NuxtLink> \u003Cbr />\r\n \u003CNuxtLink to=\"/b/id\">Link to B + param\u003C/NuxtLink>\r\n \u003C/div>\r\n\r\n \u003Cdiv>\r\n \u003CNuxtPage />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle lang=\"css\">\r\n.router-link-active {\r\n background-color: yellow;\r\n}\r\n\u003C/style>\r\n```\r\n\r\nfolder structure:\r\n```\r\nlayouts\r\n - default.vue\r\npages\r\n - a\r\n - [[id]].vue\r\n - b\r\n - [id].vue\r\n - index.vue\r\n - a.vue\r\n - b.vue\r\n```\r\n\r\n`a.vue` and `b.vue` contains:\r\n```\r\n\u003Ctemplate>\r\n \u003CNuxtPage />\r\n\u003C/template>\r\n```\r\n\r\nWorks ok for required parameter `[id]` and not properly for optional parameter `[[id]]`.\r\nAdding `.router-link-active` class works ok for `Link to B` on `/b` route and children routes like `/b/id`.\r\nSame is not working properly for `Link to A` link. Class is added only for exact route for urls `/a` and `/a/id`\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3057,3058,3061],{"name":3019,"color":3020},{"name":3059,"color":3060},"pages","00DFB5",{"name":3062,"color":3063},"upstream","E8A36D",27841,"Optional route parameter doesn't trigger active class for parent links","2025-02-10T21:37:03Z","https://github.com/nuxt/nuxt/issues/27841",0.75680244,{"description":3070,"labels":3071,"number":3073,"owner":3022,"repository":3022,"state":3037,"title":3074,"updated_at":3075,"url":3076,"score":3077},"I haven't been able to find this, and sorry if I missed it. I think this is easier to explain with an example. This may be an issue with vue-router...or an option perhaps that I could configure in the nuxt router config.\r\n\r\nI have a route `/news` with a collection of news items. Each news item will have the route `/news/title-of-news-item`, however this news item is not a nested page within the news page, but rather a new page in itself.\r\n\r\nI have a solution so in server-side rendering the correct page is loading from an API and nested correctly. When I change page I think the application is looking for a parent/child to load the page into which doesn't exist.\r\n\r\nAre there any examples of this by any chance?\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/c6900\">#c6900\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3072],{"name":3034,"color":3035},3222,"Separating Automatic Page Nesting & Routes","2023-01-18T16:12:10Z","https://github.com/nuxt/nuxt/issues/3222",0.75744694,{"labels":3079,"number":3082,"owner":3022,"repository":3022,"state":3037,"title":3083,"updated_at":3084,"url":3085,"score":3086},[3080,3081],{"name":3019,"color":3020},{"name":3034,"color":3035},6235,"Strange behaviour of nested pages ","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6235",0.7574894,{"description":3088,"labels":3089,"number":3099,"owner":3022,"repository":3100,"state":3037,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Environment\n\n\n\n- Operating System: Darwin\n- Node Version: v23.9.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, components, css, devServer, ssr, vuefire, runtimeConfig\n- Runtime Modules: @nuxt/image@1.10.0, @nuxt/ui-pro@3.0.2, nuxt-vuefire@1.0.5\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nThis is noticeable on the documentation [page](https://ui.nuxt.com/components/navigation-menu#orientation) for any vertical navigation menu with children navigation items. \n\n### Description\n\nThe parent item renders as a `\u003Cbutton>` tag instead of the `\u003Ca>` tags of other navigation menu items. This means the `to:` attribute is ignored (and target) and can't be clicked on. This is likely due to the parent and children being converted to a Collapsible component under the hood. \n\nWhen the orientation is horizontal, however, you can have both the parent and children be links - where they render `\u003Ca>` tags. Hovering over the horizontal parent shows the children, but the parent can still be a link.\n\nIdeally, we could set a boolean to control whether the children are converted to a Collapsible or not. Or wrap the Collapsible parent around a link. Understandably, the click then couldn't trigger opening/closing the collapsible (maybe the icon triggers opening/closing, while the label can still have the Link attributes available).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3090,3093,3096],{"name":3091,"color":3092},"bug","d73a4a",{"name":3094,"color":3095},"v3","49DCB8",{"name":3097,"color":3098},"triage","ffffff",3911,"ui","[NavigationMenu] Vertical menu with children doesn't respect parent Link attributes.","2025-05-10T15:51:54Z","https://github.com/nuxt/ui/issues/3911",0.7594389,{"description":3106,"labels":3107,"number":3110,"owner":3022,"repository":3022,"state":3037,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Version\n\n[v1.4.2](https://github.com/nuxt.js/releases/tag/v1.4.2)\n\n### Reproduction link\n\n[null](null)\n\n### Steps to reproduce\n\nmy pages \n\n\n\n\n\n\n### What is expected ?\n\n```\nroutes: [\n\t\t{\n\t\t\tpath: \"/brand/brief/:categoryId/:brandId\",\n\t\t\tcomponent: \"pages/brand/brief/_category/_brandId/index.vue\",\n\t\t\tname: \"brand-brief-categoryId-brandId\"\n\t\t},\n], \n```\n\n### What is actually happening?\n\n```\nroutes: [\n\t\t{\n\t\t\tpath: \"/brand/brief/:categoryId?/:brandId?\",\n\t\t\tcomponent: \"pages/brand/brief/_category/_brandId/index.vue\",\n\t\t\tname: \"brand-brief-categoryId-brandId\"\n\t\t},\n], \n```\n\n### Additional comments?\n\nI dont want that '?' , is that a bug?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7543\">#c7543\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3108,3109],{"name":3019,"color":3020},{"name":3034,"color":3035},3702,"Dynamic Nested Routes Not Support","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3702",0.75993425,{"description":3116,"labels":3117,"number":3110,"owner":3022,"repository":3100,"state":3037,"title":3121,"updated_at":3122,"url":3123,"score":3114},"### Environment\n\nnode v20\nnuxtui 2.21.0\nnuxt 3.15.4\nwindows 10\n\n### Version\n\n2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-ztjeoeq3?file=app.config.ts,app.vue\n\n### Description\n\nnotification disappears immediately without the animation class taking effect first\nin reproduction, supposedly the card will move down off screen on timeout\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3118,3119],{"name":3091,"color":3092},{"name":3120,"color":3098},"wontfix-v2","Notification (Toast) leave animation not showing","2025-03-30T16:52:58Z","https://github.com/nuxt/ui/issues/3702",{"description":3125,"labels":3126,"number":3129,"owner":3022,"repository":3022,"state":3037,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Describe the feature\n\nIn `nuxt 3.8.2`, if I want to create two nested route like `/parent/a` and `/parent/b`, I need to organize these three `.vue` file like this:\r\n```\r\n\\pages\r\n \\parent\r\n a.vue\r\n b.vue\r\n parent.vue\r\n```\r\nthen add `\u003CNuxtPage />` into `parent.vue` as `\u003CRouterView>`, and add redirect rule in `parent.vue`:\r\n```ts\r\ndefinePageMeta({\r\n redirect: '/parent/a',\r\n})\r\n```\r\nIt work well.\r\n\r\n---\r\n\r\nBut if I place these three files as the following structure:\r\n```\r\n\\pages\r\n \\parent\r\n index.vue\r\n a.vue\r\n b.vue\r\n```\r\nthis `index.vue` couldn't be execute or render.\r\nBut I think it's a better way to origainze nasted file, especially when the neste rule is complex. \r\n\n\n### Additional information\n\n- [ ] 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).",[3127,3128],{"name":3046,"color":3047},{"name":3019,"color":3020},24720,"More support for nested route","2024-01-02T11:33:45Z","https://github.com/nuxt/nuxt/issues/24720",0.76183033,["Reactive",3135],{},["Set"],["ShallowReactive",3138],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5PNKX3zDuUs5VIn8p3AHCA9dED_WIZ9IVJNq4Mqgv3M":-1},"/nuxt/ui/4255"]