René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug(router) aux-routes not working with empty-path top-level routes","articleBody":"**I'm submitting a ...**  (check one with \"x\")\n\n```\n[x] bug report\n[ ] feature request\n[ ] support request =\u003e Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question\n```\n\n**Current behavior**\n\nAux-Routes are not found when using two levels of \"default routes\" (with `path:''`).\nThis config works:\n\n``` ts\n RouterModule.forRoot([\n      {\n        path: 'tasks', component: TasksComponent, //container-component has two outlets! \n        children: [\n          { path: '', component:TaskListComponent },\n          { path: 'overview/:id', component: TasksComponent, outlet: 'right' },\n        ]\n      }\n  ],\n```\n\nI can open the Tasks-overview by doing:\n\n`http://localhost:4200/tasks/(right:overview/3)`\n\nSee this plnkr and click \"to list\", \"open aux\"\n\nAs I want to extract the whole Tasks-Functionality into a `TasksModule` I need to be able to do something like this:\n\n``` ts\n RouterModule.forRoot([\n      {\n        path: 'tasks', : children: [ // this one would be in main module\n          //this is defined in the TasksModule:\n          { path: '', component: TasksComponent, //container-component has two outlets! \n            children: [\n              { path: '', component:TaskListComponent },\n              { path: 'overview/:id', component: TasksComponent, outlet: 'right' },\n          ]\n      }\n  ],\n```\n\nI would assume both configs are equivalent, and all of the \"normal\" routing works perfectly fine. But now the link above `http://localhost:4200/tasks/(right:overview/3)` leads to:\n\n`Uncaught (in promise): Error: Cannot match any routes: 'tasks'`\n\nSee this plnkr: http://plnkr.co/edit/xd77Mkpqfq6U9tKM4USU?p=preview\n\n**Expected/desired behavior**\n\nAux-Routes should also work with empty-path parents\n\n**Reproduction of the problem**\n\nWorking version: http://plnkr.co/edit/Twx4hXQ0TLfHfrYSe4MO?p=preview\nNon-working version:  http://plnkr.co/edit/xd77Mkpqfq6U9tKM4USU?p=preview\n\n**What is the expected behavior?**\n\nBoth versions of route definition should lead to the same behavior\n\n**What is the motivation / use case for changing the behavior?**\n\nWith the current implementation it is impossible to create an encapsulated Config / Module for the tasks behaviour and include it under a certain path into the main config e.g. \"myTasks\". \n\n/cc @vsavkin \n\n**Please tell us about your environment:**\n- **Angular version:** 2.0.0-rc.5\n- **Browser:** [all ] \n- **Language:** [TS ]","author":{"url":"https://github.com/choeller","@type":"Person","name":"choeller"},"datePublished":"2016-08-12T09:07:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":46},"url":"https://github.com/10726/angular/issues/10726"}