Feature request: Router navigateById

I’m submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[v] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

Unable to restore previous history state by NavigationId

Expected behavior

Able to navigate to previous state simply by it’s id.

Will be great to have router method navigateById

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

You added id to router.events, to determine states history. You added restoredState to NavigationStart to determine restoration of previous router states. But, there is no option to navigate by this id.

[dawidgarus]

@glebmachine It’s still possible to do it yourself. I know because I’ve done that before, sadly I cannot share code. You would need to provide your own LocationStrategy, keep a stack with navigation ids which would be manipulated accordingly on pushState/replaceState/popState/NavigationEnd (really tricky to do it right) and use window.history.go - the stack will provide information how far You want to go.

[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.}