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
2.4 KiB
@cheatsheetSection
Routing and navigation
@cheatsheetIndex 10
@description
import {RouteConfig, ROUTER_DIRECTIVES, ROUTER_PROVIDERS, ...} from 'angular2/router';
@cheatsheetItem
@RouteConfig([ { path: '/:myParam', component: MyComponent, as: 'MyCmp' }, { path: '/staticPath', component: ..., as: ...}, { path: '/*wildCardParam', component: ..., as: ...} ]) class MyComponent() {}
|@RouteConfig
Configures routes for the decorated component. Supports static, parameterized and wildcard routes.
@cheatsheetItem
<router-outlet></router-outlet>
|router-outlet
Marks the location to load the component of the active route.
@cheatsheetItem
<a [router-link]="[ '/MyCmp', {myParam: 'value' } ]">
|[router-link]
Creates a link to a different view based on a route instruction consisting of a route name and optional parameters. The route name matches the as property of a configured route. Add the '/' prefix to navigate to a root route; add the './' prefix for a child route.
@cheatsheetItem
@CanActivate(() => { ... })class MyComponent() {}
|@CanActivate
A component decorator defining a function that the router should call first to determine if it should activate this component. Should return a boolean or a promise.
@cheatsheetItem
routerOnActivate(nextInstruction, prevInstruction) { ... }
|routerOnActivate
After navigating to a component, the router calls component's routerOnActivate method (if defined).
@cheatsheetItem
routerCanReuse(nextInstruction, prevInstruction) { ... }
|routerCanReuse
The router calls a component's routerCanReuse method (if defined) to determine whether to reuse the instance or destroy it and create a new instance. Should return a boolean or a promise.
@cheatsheetItem
routerOnReuse(nextInstruction, prevInstruction) { ... }
|routerOnReuse
The router calls the component's routerOnReuse method (if defined) when it re-uses a component instance.
@cheatsheetItem
routerCanDeactivate(nextInstruction, prevInstruction) { ... }
|routerCanDeactivate
The router calls the routerCanDeactivate methods (if defined) of every component that would be removed after a navigation. The navigation proceeds if and only if all such methods return true or a promise that is resolved.
@cheatsheetItem
routerOnDeactivate(nextInstruction, prevInstruction) { ... }
|routerOnDeactivate
Called before the directive is removed as the result of a route change. May return a promise that pauses removing the directive until the promise resolves.