chore(links): fix broken links in dev guides
This commit is contained in:
parent
a48b307aed
commit
0e8d7afc08
|
@ -521,8 +521,8 @@ figure.image-display
|
|||
Recall from the previous section that `ngControl` registered this input box with the
|
||||
`NgForm` directive as "name".
|
||||
|
||||
We didn't add the `NgForm`<!-- TODO: link to (../api/core/NgForm-class.html) --> directive explicitly.
|
||||
Angular added it surreptitiously, wrapping it around the `<form>` element.
|
||||
We didn't add the **[`NgForm`](../api/common/NgForm-directive.html) directive*
|
||||
explicitly. Angular added it surreptitiously, wrapping it around the `<form>` element.
|
||||
|
||||
The `NgForm` directive supplements the `<form>` element with additional features.
|
||||
It collects controls (elements identified by an `ngControl` directive)
|
||||
|
|
|
@ -488,7 +488,7 @@ figure.image-display
|
|||
:marked
|
||||
### The NgForm directive
|
||||
We just set a template local variable with the value of an `NgForm` directive.
|
||||
Why did that work? We didn't add the **[`NgForm`](../api/core/NgForm-class.html) directive** explicitly.
|
||||
Why did that work? We didn't add the **[`NgForm`](../api/common/NgForm-directive.html) directive** explicitly.
|
||||
|
||||
Angular added it surreptiously, wrapping it around the `<form>` element
|
||||
|
||||
|
|
|
@ -452,7 +452,7 @@ code-example(format="").
|
|||
We might load it on a mobile device with [Apache Cordova](https://cordova.apache.org/) or [NativeScript](https://www.nativescript.org/).
|
||||
We might wish to render the first page of our application on the server
|
||||
to improve launch performance or facilitate
|
||||
[SEO](http://static.googleusercontent.com/media/www.google.com/en//webmasters/docs/search-engine-optimization-starter-guide.pdf).
|
||||
[SEO](http://www.google.com/webmasters/docs/search-engine-optimization-starter-guide.pdf).
|
||||
|
||||
These targets require a different kind of bootstrap function that we'd import from a different library.
|
||||
|
||||
|
|
|
@ -38,7 +38,7 @@ include ../_util-fns
|
|||
## Pass data from parent to child with input binding
|
||||
|
||||
`HeroChildComponent` has two ***input properties***,
|
||||
typically adorned with [@Input decorations](/docs/ts/latest/guide/template-syntax.html#inputs-outputs).
|
||||
typically adorned with [@Input decorations](../guide/template-syntax.html#inputs-outputs).
|
||||
|
||||
+makeExample('cb-component-communication/ts/app/hero-child.component.ts')
|
||||
:marked
|
||||
|
@ -142,7 +142,7 @@ figure.image-display
|
|||
The parent binds to that event property and reacts to those events.
|
||||
|
||||
The child's `EventEmitter` property is an ***output property***,
|
||||
typically adorned with an [@Output decoration](/docs/ts/latest/guide/template-syntax.html#inputs-outputs)
|
||||
typically adorned with an [@Output decoration](../guide/template-syntax.html#inputs-outputs)
|
||||
as seen in this `VoterComponent`:
|
||||
|
||||
+makeExample('cb-component-communication/ts/app/voter.component.ts')
|
||||
|
|
|
@ -883,7 +883,8 @@ code-example(format="").
|
|||
## Router Lifecycle Hooks
|
||||
|
||||
Angular components have [lifecycle hooks](lifecycle-hooks.html). For example, Angular calls the hook methods of the
|
||||
[OnInit](../api/core/OnInit-interface.html) and [OnDestroy](../api/core/OnDestroy-interface.html)
|
||||
[OnInit](../api/core/OnInit-interface.html) and [OnDestroy](../api/common/OnDestroy-interface
|
||||
.html)
|
||||
interfaces when it creates and destroys components.
|
||||
|
||||
The router also has hooks for *its* lifecycle such as
|
||||
|
@ -1375,7 +1376,8 @@ code-example(format="." language="bash").
|
|||
|
||||
Angular detects when a component has certain lifecycle methods like
|
||||
[ngOnInit](https://angular.io/docs/ts/latest/api/core/OnInit-interface.html) and
|
||||
[ngOnDestroy](https://angular.io/docs/ts/latest/api/core/OnDestroy-interface.html) and calls them
|
||||
[ngOnDestroy](https://angular.io/docs/ts/latest/api/common/OnDestroy-interface.html) and calls
|
||||
them
|
||||
at the appropriate moment.
|
||||
|
||||
Angular will call `ngOnInit` when we navigate to the `HeroDetailComponent`, we'll get the `id` from the `RouteParams`
|
||||
|
|
|
@ -286,7 +286,7 @@ a(id="main")
|
|||
We might load it on a mobile device with [Apache Cordova](https://cordova.apache.org/) or [NativeScript](https://www.nativescript.org/).
|
||||
We might wish to render the first page of our application on the server
|
||||
to improve launch performance or facilitate
|
||||
[SEO](http://static.googleusercontent.com/media/www.google.com/en//webmasters/docs/search-engine-optimization-starter-guide.pdf).
|
||||
[SEO](http://www.google.com/webmasters/docs/search-engine-optimization-starter-guide.pdf).
|
||||
|
||||
These targets require a different kind of bootstrap function that we'd import from a different library.
|
||||
|
||||
|
|
Loading…
Reference in New Issue