604c8bbad5
BREAKING CHANGE: Previously, components that would implement lifecycle interfaces would include methods like "onChanges" or "afterViewInit." Given that components were at risk of using such names without realizing that Angular would call the methods at different points of the component lifecycle. This change adds an "ng" prefix to all lifecycle hook methods, far reducing the risk of an accidental name collision. To fix, just rename these methods: * onInit * onDestroy * doCheck * onChanges * afterContentInit * afterContentChecked * afterViewInit * afterViewChecked * _Router Hooks_ * onActivate * onReuse * onDeactivate * canReuse * canDeactivate To: * ngOnInit, * ngOnDestroy, * ngDoCheck, * ngOnChanges, * ngAfterContentInit, * ngAfterContentChecked, * ngAfterViewInit, * ngAfterViewChecked * _Router Hooks_ * routerOnActivate * routerOnReuse * routerOnDeactivate * routerCanReuse * routerCanDeactivate The names of lifecycle interfaces and enums have not changed, though interfaces have been updated to reflect the new method names. Closes #5036 |
||
|---|---|---|
| .. | ||
| impl | ||
| README.md | ||
| async_route_spec.ts | ||
| auxiliary_route_spec.ts | ||
| bootstrap_spec.ts | ||
| lifecycle_hook_spec.ts | ||
| navigation_spec.ts | ||
| redirect_route_spec.ts | ||
| router_link_spec.ts | ||
| sync_route_spec.ts | ||
| util.ts | ||
README.md
Router integration tests
These tests only mock out Location, and otherwise use all the real parts of routing to ensure that
various routing scenarios work as expected.
The Component Router in Angular 2 exposes only a handful of different options, but because they can be combined and nested in so many ways, it's difficult to rigorously test all the cases.
The address this problem, we introduce describeRouter, describeWith, and describeWithout.