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

docs: remove inappropriate link (#31091) 

PR Close #31091
This commit is contained in:
Judy Bogart 2019-06-17 09:27:11 -07:00 committed by Kara Erickson
parent 4ec50811d4
commit ab86a58f27
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
packages/common/src/location/location.ts
View File

@ -25,7 +25,7 @@ export interface PopStateEvent {
* *
* A service that applications can use to interact with a browser's URL. * A service that applications can use to interact with a browser's URL.
* *
* Depending on the {@link LocationStrategy} used, `Location` will either persist * Depending on the `LocationStrategy` used, `Location` will either persist
* to the URL's path or the URL's hash segment. * to the URL's path or the URL's hash segment.
* *
* @usageNotes * @usageNotes
@ -43,7 +43,8 @@ export interface PopStateEvent {
* *
* ### Example * ### Example
* *
* {@example common/location/ts/path_location_component.ts region='LocationComponent'} * <code-example path='common/location/ts/path_location_component.ts'
* region='LocationComponent'></code-example>
* *
* @publicApi * @publicApi
*/ */

17
packages/common/src/location/location_strategy.ts
View File

@ -10,18 +10,17 @@ import {InjectionToken} from '@angular/core';
import {LocationChangeListener} from './platform_location'; import {LocationChangeListener} from './platform_location';
/** /**
* `LocationStrategy` is responsible for representing and reading route state * Enables the `Location` service to read route state from the browser's URL.
* from the browser's URL. Angular provides two strategies: * Angular provides two strategies:
* {@link HashLocationStrategy} and {@link PathLocationStrategy}. * `HashLocationStrategy` and `PathLocationStrategy`.
* *
* This is used under the hood of the {@link Location} service. * Applications should use the `Router` or `Location` services to
*
* Applications should use the {@link Router} or {@link Location} services to
* interact with application route state. * interact with application route state.
* *
* For instance, {@link HashLocationStrategy} produces URLs like * For instance, `HashLocationStrategy` produces URLs like
* `http://example.com#/foo`, and {@link PathLocationStrategy} produces * <code class="no-auto-link">http://example.com#/foo</code>,
* `http://example.com/foo` as an equivalent URL. * and `PathLocationStrategy` produces
* <code class="no-auto-link">http://example.com/foo</code> as an equivalent URL.
* *
* See these two classes for more. * See these two classes for more.
* *