iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(zone.js): Typos on zone.md file and fixes on code examples. (#36138) 

1. During reading the documentation I found some code examples that were refering to the class properties via methods, but without specifying the context `this`.
2. The 'onInvoke' hook was duplicated
3. A minor typo on `Zones and execution contexts` section
4. A minor typo on `Zones and async lifecycle hooks` section

PR Close #36138
This commit is contained in:
profanis 2020-03-16 21:53:44 +02:00 committed by Misko Hevery
parent c21c46a8e8
commit d25012e864
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
aio/content/guide/zone.md
View File

@ -117,12 +117,13 @@ To understand how change detection works, first consider when the application ne
}) })
export class AppComponent implements OnInit { export class AppComponent implements OnInit {
data = 'initial value'; data = 'initial value';
serverUrl = 'SERVER_URL';
constructor(private httpClient: HttpClient) {} constructor(private httpClient: HttpClient) {}
ngOnInit() { ngOnInit() {
this.httpClient.get(serverUrl).subscribe(response => { this.httpClient.get(this.serverUrl).subscribe(response => {
// user does not need to trigger change detection manually // user does not need to trigger change detection manually
data = response.data; this.data = response.data;
}); });
} }
} }
@ -141,7 +142,7 @@ export class AppComponent implements OnInit {
ngOnInit() { ngOnInit() {
setTimeout(() => { setTimeout(() => {
// user does not need to trigger change detection manually // user does not need to trigger change detection manually
data = 'value updated'; this.data = 'value updated';
}); });
} }
} }
@ -160,7 +161,7 @@ export class AppComponent implements OnInit {
ngOnInit() { ngOnInit() {
Promise.resolve(1).then(v => { Promise.resolve(1).then(v => {
// user does not need to trigger change detection manually // user does not need to trigger change detection manually
data = v; this.data = v;
}); });
} }
} }
@ -200,7 +201,7 @@ func.apply(ctx2);
The value of `this` in the callback of `setTimeout` might differ depending on when `setTimeout` is called. The value of `this` in the callback of `setTimeout` might differ depending on when `setTimeout` is called.
Thus you can lose the context in asynchronous operations. Thus you can lose the context in asynchronous operations.
A zone provides a new zone context other than `this`, the zone context persists across asynchronous operations. A zone provides a new zone context other than `this`, the zone context that persists across asynchronous operations.
In the following example, the new zone context is called `zoneThis`. In the following example, the new zone context is called `zoneThis`.
```javascript ```javascript
@ -257,16 +258,14 @@ The Zone Task concept is very similar to the Javascript VM Task concept.
- `microTask`: such as `Promise.then()`. - `microTask`: such as `Promise.then()`.
- `eventTask`: such as `element.addEventListener()`. - `eventTask`: such as `element.addEventListener()`.
The `onInvoke` hook triggers when a synchronize function is executed in a Zone.
These hooks trigger under the following circumstances: These hooks trigger under the following circumstances:
- `onScheduleTask`: triggers when a new asynchronous task is scheduled, such as when you call `setTimeout()`. - `onScheduleTask`: triggers when a new asynchronous task is scheduled, such as when you call `setTimeout()`.
- `onInvokeTask`: triggers when an asynchronous task is about to execute, such as when the callback of `setTimeout()` is about to execute. - `onInvokeTask`: triggers when an asynchronous task is about to execute, such as when the callback of `setTimeout()` is about to execute.
- `onHasTask`: triggers when the status of one kind of task inside a zone changes from stable to unstable or from unstable to stable. A status of stable means there are no tasks inside the Zone, while unstable means a new task is scheduled in the zone. - `onHasTask`: triggers when the status of one kind of task inside a zone changes from stable to unstable or from unstable to stable. A status of stable means there are no tasks inside the Zone, while unstable means a new task is scheduled in the zone.
- `onInvoke`: triggers when a synchronize function is going to execute in the zone. - `onInvoke`: triggers when a synchronous function is going to execute in the zone.
With these hooks, `Zone` can monitor the status of all synchronize and asynchronous operations inside a zone. With these hooks, `Zone` can monitor the status of all synchronous and asynchronous operations inside a zone.
The above example returns the following output. The above example returns the following output.