when using router.navigate(…) with relative url, angular should warn if { relativeTo} is not set · Issue #26027 · angular/angular · GitHub
![typescript - Router getCurrentNavigation always returns null only after upgrading to angular 15 - Stack Overflow typescript - Router getCurrentNavigation always returns null only after upgrading to angular 15 - Stack Overflow](https://i.stack.imgur.com/zs5DS.png)
typescript - Router getCurrentNavigation always returns null only after upgrading to angular 15 - Stack Overflow
![Using "replaceUrl" In Order To Honor The Back-Button While Chaining Absolute Redirects In Angular 7.2.13 Using "replaceUrl" In Order To Honor The Back-Button While Chaining Absolute Redirects In Angular 7.2.13](https://bennadel-cdn.com/resources/uploads/2019/router-chained-redirects-replace-url-angular7.png)