Skip to content

Commit 890abac

Browse files
trentvbtjvantoll
authored andcommitted
Update list-view.md
Wording change. Closes NativeScript#568
1 parent bb3415f commit 890abac

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

ui/list-view.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ As shown just creating a custom component and add it to directives of the host c
164164

165165
### Using async pipe
166166

167-
Generally according to Angular documentation pipe is a simple display-value transformation that can be declared in HTML. Pipe takes an input and transforms it to a desired output. One of the built-in Angular pipes is very commonly used with ListView like controls. This is the `async` pipe. The input of this pipe is either `Promise<Array>` or `Observable<Array>` (Observable actually stands for [RxJS.Observable](https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/observable.md). What this pipe do is to subscribe for the observable and return the value inside it as property value. Following is a simple example of using async pipe with NativeScript-Angular ListView.
167+
Generally according to Angular documentation pipe is a simple display-value transformation that can be declared in HTML. Pipe takes an input and transforms it to a desired output. One of the built-in Angular pipes is very commonly used with ListView like controls. This is the `async` pipe. The input of this pipe is either `Promise<Array>` or `Observable<Array>` (Observable actually stands for [RxJS.Observable](https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/observable.md). This pipe subscribes to the observable and returns the value inside it as property value. Following is a simple example of using async pipe with NativeScript-Angular ListView.
168168

169169
```TypeScript
170170
import { Component, Input, ChangeDetectionStrategy } from '@angular/core';

0 commit comments

Comments
 (0)