Angular 2 Data Flow – Jeff Cross, Rob Wormald and Alex Rickabaugh
Why Stack Overflow recommends it
Stack Overflow users link it as a reference when explaining Angular 2 observables, pipes, and the early design ideas behind data flow and template variables.
Recommended by 3 people across 2 different months, 2015 to 2016.
What it is
A 2015 AngularConnect conference talk in which members of the Angular team explain how data flows through Angular 2 apps. It covers observables and event subscription, how pipes relate to Angular 1 filters, and whether $digest still matters.
What people said
Recommends Thierry Templier · 2016-01 · Stack Overflow · on “Angular2 http.get() ,map(), subscribe() and observable pattern - basic understanding”
Concepts Observables in short tackles asynchronous processing and events. Comparing to promises this could be described as observables = promises + events. What is great with observables is that they are lazy, they can be canceled and you can apply some operators in them (like map , ...). This allows to handle asynchronous things in a very flexible way. A great sample describing the best the power of observables is the way to connect a filter input to a corresponding filtered list. When the user enters characters, the list is refreshed. Observables handle corresponding AJAX requests and cancel previous in-progress requests if another one is triggered by new value in the input. Here is the co
Recommends ABabin · 2016-08 · Stack Overflow · on “what is eventemitter and eventemitter service. How we use Event emitter without @output and @input?”
Read this Angular cookbook about component interaction and flow, [LINK] especially this [LINK] part about parent components listening for child events. Basically, EventEmitters are intended exactly for the purpose of parent components getting data from children. All @Outputs are EventEmitters and the @Output decorator exposes an event that parents can attach listeners to in its template. In the child component, you define an EventEmitter like so: @Output() childEventEmitter = new EventEmitter<any>(); You emit events like this: this.childEventEmitter.emit("Send this to the parent"); With that done, the parent can listen for the event and attach a callback with nothing more than this: <child-c
Recommends candidJ · 2016-08 · Stack Overflow · on “Angular2 http.get() ,map(), subscribe() and observable pattern - basic understanding”
@StavAlfi `pipes` are also an `observables`. check out this video : [this video] suggested by thierry for more info.
Cites puffy · 2015-11 · Stack Overflow · on “Object.observe withdrawal and RxJS and Angular 2”
I am a bit confused, because Obejct.observe is said to be withdrawn from the ES2016 [LINK] . On the other hand there were talks on Angular Connect [this video] that mentions they will rely on it. So as far I understand Angular 2 doesn't rely on Object.observe directly but on RxJS which do use the Object.observe Can you please help me understand the impacts of this withdrawal ? I am also confused how this will influence the functional reactive javascript development. Sorry if it's stupid question, but all these concepts are really new to me.
Cites Dizzy · 2016-05 · Stack Overflow · on “There is no ng-init for Angular2”
As we all know there is no ng-init or something for Angular2. So if we try do do something like: <div #rr="2+2"> {{rr}} </div> We will get runtime error: Error: There is no directive with "exportAs" set to "2+2" I was watching one of the Angular2 dev videos on [this video] and saw exactly the same construction meant to work. Here is the screenshot: [LINK] How is this assignment to user template variable possible?