feature(router): warn if navigation triggered outside Angular zone #24728
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release) [ ] Bug report [ ] Performance issue [x] 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
When some user performs navigation outside the Angular zone, the change detection will not be invoked.
Even it's certainly users' fault, they may still going to be confused by what the problem is:
- Router: change detection doesn't work with manual initial navigation (is it a bug?) #15770
- Router can't navigate when exception occurrs #15946
- Using router.navigate to navigate to another component does not invoke the onInit method #18254
- Angular freezes without any error when I navigate to next page from an external library callback #19731
- Angular 5 & 4.4.x - Router Navigate does not activate onInit after external request #20112
- On navigate() router method ngOnInit of target component is not called #22472
- Change detection is not working with router navigation #23697
- Wrong router behavior when injected in custom error handler #24727
- ...
Expected behavior
As the navigation should always happen in Angular zone, so router itself could guard against that thus produce a warning when not valid.
Minimal reproduction of the problem with instructions
N/A.
What is the motivation / use case for changing the behavior?
Reduce the invalid issue amounts.
Environment
Angular version: X.Y.Z Browser: - [ ] Chrome (desktop) version XX - [ ] Chrome (Android) version XX - [ ] Chrome (iOS) version XX - [ ] Firefox version XX - [ ] Safari (desktop) version XX - [ ] Safari (iOS) version XX - [ ] IE version XX - [ ] Edge version XX For Tooling issues: - Node version: XX - Platform: Others: