Passing members from a parent component into a child component

With the departure of the Angular 1.x concept of $scope inheritance, mentally (partially or entirely) remodeling how information would be passed around your application is a must. In its place, you have an entirely new system of propagating information throughout the application's hierarchy.

Gone also is the concept of defaulting to bidirectional data binding. Although it made for an application that was simpler to reason about, bidirectional data binding incurs an unforgivably expensive drag on performance. This new system operates in an asymmetric fashion: members are propagated downwards through the component tree, but not upwards unless explicitly performed.

Note

The code, links, ...

Get Angular 2 Cookbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.