Note: for support questions, please use one of these channels: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.

• *I'm submitting a ... *
  [ ] bug report
  [x] feature request
  [ ] support request => Please do not submit support request here, see note at the top of this template.
• Do you want to request a feature or report a bug?

Feature

• What is the current behavior?

When navigating to the same route more than once, the route components in the route tree are reused.

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
  https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
• What is the expected behavior?

The reload function is called, and all routes in the current instruction reload without being reused.

• What is the motivation / use case for changing the behavior?

There are cases where the user would want to force a reload of an entire route to go through the entire navigation process again including triggering lifecycle events.

• Please tell us about your environment:
• Angular version: 2.0.0-beta.X
• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
• Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]

All

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

This was the result of a conversation with @petebacondarwin about adding a reload feature for the router. This issue is to officially track that item. #7163 (comment)