docs: in links use href=foo#bar not foo#!#bar (#2807)

This commit is contained in:
Patrice Chalin 2016-11-15 15:36:34 -08:00 committed by Kathy Walrath
parent 64bce18ea7
commit 0dfda08306
17 changed files with 22 additions and 22 deletions

View File

@ -31,6 +31,6 @@ block module-id
:marked
Note that special measures must be taken in Angular2 for TypeScript, if
relative URLs are to have the same interpretation. See
[here](../../../ts/latest/guide/component-styles.html#!#relative-urls)
[here](../../../ts/latest/guide/component-styles.html#relative-urls)
for details.

View File

@ -63,7 +63,7 @@ code-example(language="bash").
All of our component names end in "Component". All of our component file names end in "_component".
We spell our filenames in lower **underscore case**
(AKA **[snake_case](../guide/glossary.html#!#snake_case)**) so we don't worry about
(AKA **[snake_case](../guide/glossary.html#snake_case)**) so we don't worry about
case sensitivity on the server or in source control.
<!-- TODO

View File

@ -67,7 +67,7 @@ code-example(language="bash").
.l-sub-section
:marked
We've adopted a convention in which we spell the name of a service in lowercase followed by `_service`.
If the service name were multi-word, we'd spell the base filename in lower underscore case (also called [snake_case](../guide/glossary.html#!#snake_case)).
If the service name were multi-word, we'd spell the base filename in lower underscore case (also called [snake_case](../guide/glossary.html#snake_case)).
The `SpecialSuperHeroService` would be defined in the `special_super_hero_service.dart` file.
:marked
We name the class `HeroService`.

View File

@ -36,7 +36,7 @@ block http-library
Update `pubspec.yaml` to look like this (additions are highlighted):
[guide-http]: ../guide/server-communication.html#!#http-providers
[guide-http]: ../guide/server-communication.html#http-providers
[ng2x]: https://github.com/angular/angular/wiki/Angular-2-Dart-Transformer
- var stylePattern = { pnk: /(http.*|stream.*|resolved_identifiers:|Browser.*|Client.*)/gm };

View File

@ -111,7 +111,7 @@ code-example(language="sh" class="code-shell").
h3#add-config-files (b) Add #{_package_and_config_files}
block package-and-config-files
- var _tsconfigUri = 'guide/typescript-configuration.html#tsconfig'
- var _typingsUri = 'guide/typescript-configuration.html#!#typings'
- var _typingsUri = 'guide/typescript-configuration.html#typings'
p Add the following package definition and configuration files to the project folder:
ul

View File

@ -181,7 +181,7 @@ block angular-router
.callout.is-important
header base href is essential
:marked
See the *base href* section of the [Router](../guide/router.html#!#base-href)
See the *base href* section of the [Router](../guide/router.html#base-href)
chapter to learn why this matters.
a#configure-routes
@ -334,7 +334,7 @@ block redirect-vs-use-as-default
.l-sub-section
:marked
Learn about the *redirects* in the [Routing](../guide/router.html#!#redirect) chapter.
Learn about the *redirects* in the [Routing](../guide/router.html#redirect) chapter.
:marked
#### Add navigation to the template
@ -872,7 +872,7 @@ block css-files
Our designers provided some basic styles to apply to elements across the entire app.
These correspond to the full set of master styles that we
introduced earlier (see
[QuickStart, "Add some style"](../quickstart.html#!#add-some-style)).
[QuickStart, "Add some style"](../quickstart.html#add-some-style)).
Here is an excerpt:
+makeExcerpt('styles.css (excerpt)', 'toh')

View File

@ -112,7 +112,7 @@ block dont-be-distracted-by-backend-subst
This chapter is an introduction to the !{_Angular_http_library}.
Please don't be distracted by the details of this backend substitution. Just follow along with the example.
Learn more later about the in-memory web API in the [HTTP client chapter](../guide/server-communication.html#!#in-mem-web-api).
Learn more later about the in-memory web API in the [HTTP client chapter](../guide/server-communication.html#in-mem-web-api).
Remember, the in-memory web API is only useful in the early stages of development and for demonstrations such as this Tour of Heroes.
Skip it when you have a real web API server.

View File

@ -77,7 +77,7 @@ a#modularity
In both _TypeScript_ and _ES6_, you import Angular classes, functions, and other members with _ES6_ `import` statements.
In _ES5_, you access the Angular entities of the [the Angular packages](../glossary.html#!#scoped-package)
In _ES5_, you access the Angular entities of the [the Angular packages](../glossary.html#scoped-package)
through the global `ng` object.
Anything you can import from `@angular` is a nested member of this `ng` object:

View File

@ -283,7 +283,7 @@ block ctor-syntax
.l-sub-section
:marked
Read also **Should I add app-wide providers to the root `AppModule` or the root `AppComponent`?** in the [NgModule FAQ](../cookbook/ngmodule-faq.html#!#q-root-component-or-module) chapter.
Read also **Should I add app-wide providers to the root `AppModule` or the root `AppComponent`?** in the [NgModule FAQ](../cookbook/ngmodule-faq.html#root-component-or-module) chapter.
:marked
### Preparing the HeroListComponent for injection

View File

@ -74,7 +74,7 @@ a(id="dependencies")
***@angular/platform-browser*** - Everything DOM and browser related, especially the pieces that help render into DOM.
This package also includes the bootstrapStatic method for bootstrapping applications for production builds that pre-compile templates offline.
***@angular/platform-browser-dynamic*** - Includes [Providers](../api/core/index/Provider-type-alias.html) and a [bootstrap](ngmodule.html#!#bootstrap) method for applications that
***@angular/platform-browser-dynamic*** - Includes [Providers](../api/core/index/Provider-type-alias.html) and a [bootstrap](ngmodule.html#bootstrap) method for applications that
compile templates on the client. Dont use offline compilation.
Use this package for bootstrapping during development and for bootstrapping plunker samples.

View File

@ -583,7 +583,7 @@ h3#router-directives <i>Router Directives</i>
* separates our routing concerns from our feature module
* provides a module to replace or remove when testing our feature module
* provides a common place for require routing service providers including guards and resolvers
* is **not** concerned with feature [module declarations](../cookbook/ngmodule-faq.html#!#routing-module)
* is **not** concerned with feature [module declarations](../cookbook/ngmodule-faq.html#routing-module)
:marked
### Refactor routing into a module

View File

@ -1821,7 +1821,7 @@ a(href="#toc") Back to top
.s-why.s-why-last
:marked
**Why?** Angular allows for an [alternative syntax](template-syntax.html#!#binding-syntax) `on-*`. If the event itself was prefixed with `on` this would result in an `on-onEvent` binding expression.
**Why?** Angular allows for an [alternative syntax](template-syntax.html#binding-syntax) `on-*`. If the event itself was prefixed with `on` this would result in an `on-onEvent` binding expression.
+makeExample('style-guide/ts/05-16/app/heroes/hero.component.avoid.ts', 'example', 'app/heroes/hero.component.ts')(avoid=1)
:marked

View File

@ -721,7 +721,7 @@ figure
+makeExample('upgrade-module/ts/app/1-to-2-providers/heroes.service.ts', null, 'heroes.service.ts')
:marked
We can upgrade the service using a Angular 2 [Factory provider](../guide/dependency-injection.html#!#factory-providers)
We can upgrade the service using a Angular 2 [Factory provider](../guide/dependency-injection.html#factory-providers)
that requests the service from the Angular 1 `$injector`. The name of the Angular 2 dependency is up to you:
+makeExample('upgrade-module/ts/app/1-to-2-providers/app.module.ts', 'register', 'app.module.ts')

View File

@ -64,8 +64,8 @@ code-example(language="bash").
All of our component names end in "Component". All of our component file names end in ".component".
We spell our file names in lower **[dash case](../guide/glossary.html#!#dash-case)**
(AKA **[kebab-case](../guide/glossary.html#!#kebab-case)**) so we don't worry about
We spell our file names in lower **[dash case](../guide/glossary.html#dash-case)**
(AKA **[kebab-case](../guide/glossary.html#kebab-case)**) so we don't worry about
case sensitivity on the server or in source control.
<!-- TODO

View File

@ -70,7 +70,7 @@ code-example(language="bash").
.l-sub-section
:marked
We've adopted a convention in which we spell the name of a service in lowercase followed by `.service`.
If the service name were multi-word, we'd spell the base filename in lower [dash-case](../guide/glossary.html#!#dash-case).
If the service name were multi-word, we'd spell the base filename in lower [dash-case](../guide/glossary.html#dash-case).
The `SpecialSuperHeroService` would be defined in the `special-super-hero.service.ts` file.
:marked
We name the class `HeroService` and export it for others to import.

View File

@ -181,7 +181,7 @@ block angular-router
.callout.is-important
header base href is essential
:marked
See the *base href* section of the [Router](../guide/router.html#!#base-href)
See the *base href* section of the [Router](../guide/router.html#base-href)
chapter to learn why this matters.
a#configure-routes
@ -334,7 +334,7 @@ block redirect-vs-use-as-default
.l-sub-section
:marked
Learn about the *redirects* in the [Routing](../guide/router.html#!#redirect) chapter.
Learn about the *redirects* in the [Routing](../guide/router.html#redirect) chapter.
:marked
#### Add navigation to the template
@ -889,7 +889,7 @@ block css-files
Our designers provided some basic styles to apply to elements across the entire app.
These correspond to the full set of master styles that we
introduced earlier (see
[QuickStart, "Add some style"](../quickstart.html#!#add-some-style)).
[QuickStart, "Add some style"](../quickstart.html#add-some-style)).
Here is an excerpt:
+makeExcerpt('styles.css (excerpt)', 'toh')

View File

@ -112,7 +112,7 @@ block dont-be-distracted-by-backend-subst
This chapter is an introduction to the !{_Angular_http_library}.
Please don't be distracted by the details of this backend substitution. Just follow along with the example.
Learn more later about the in-memory web API in the [HTTP client chapter](../guide/server-communication.html#!#in-mem-web-api).
Learn more later about the in-memory web API in the [HTTP client chapter](../guide/server-communication.html#in-mem-web-api).
Remember, the in-memory web API is only useful in the early stages of development and for demonstrations such as this Tour of Heroes.
Skip it when you have a real web API server.