Query string being is being treated as a path segment for route matching

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Query string being is being treated as a path segment for route matching

RouterModule.forRoot([
  { path: 'items/all', component: AllItemsComponent }
  { path: 'items/:id/:alias', component: SingleItemComponent }
]);

• Navigating to /items/all?param=x shows AllItemsComponent
• Navigating to /items/all/?param=x shows SingleItemComponent
• Navigating to /items/all/ redirects to /items/all

Expected/desired behavior

• Navigating to /items/all?param=x shows AllItemsComponent
• Navigating to /items/all/?param=x shows AllItemsComponent or redirects to /items/all?param=x

It would be nice if we could provide a regex for matching routes, rather than just a simple path. This could be solved in the back-end but that is very annoying to have to do.

Reproduction of the problem

See above - sorry I don’t know how to demonstrate this using plnkr since it requires navigating directly to a page.

What is the expected behavior?

See above

What is the motivation / use case for changing the behavior? If /path/ behaves the same as /path, then /path/?query should behave the same as /path?query

Please tell us about your environment:

• Angular version: 2.0.0-rc.5
• Browser: all
• Language: TypeScript 1.8

[zoechi]

Plunker would still be a complete runnable example that shows how you configured and connected stuff even when it doesn’t allow to reproduce the issue.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}