Okay, I have two use cases for my question here:
I\'m working on an application which has a /en/register
route. It all works good when I\'m at t
When I needed to "reload" the current component's constructor and ngOnInit functions, the only solution I found was kind of a workaround:
I used the fact that "this.router.navigate" returns a promise. So I navigated somewhere else, and returned. It's a bit ugly but it works and the UI is not affected:
this.router.navigate(..[somewhere else]..)
.then(()=>{this.router.navigate(..back..)})
Hope it helps.