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

docs(common): remove mention of the deprecated (#36953) 

web worker platform. Minor grammar/stylistic changes.

Inline documentation for the PlatformLocation service instead mentions @angular/platform-server.

Typos corrected, minor grammar and stylistic changes.

PR Close #36953
This commit is contained in:
Lars Gyrup Brink Nielsen 2020-05-06 20:44:55 +02:00 committed by Alex Rickabaugh
parent fdd61152c5
commit 14be55c9fa
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
packages/common/src/location/platform_location.ts
View File

@ -14,21 +14,21 @@ import {DOCUMENT} from '../dom_tokens';
* This class should not be used directly by an application developer. Instead, use * This class should not be used directly by an application developer. Instead, use
* {@link Location}. * {@link Location}.
* *
* `PlatformLocation` encapsulates all calls to DOM apis, which allows the Router to be platform * `PlatformLocation` encapsulates all calls to DOM APIs, which allows the Router to be
* agnostic. * platform-agnostic.
* This means that we can have different implementation of `PlatformLocation` for the different * This means that we can have different implementation of `PlatformLocation` for the different
* platforms that angular supports. For example, `@angular/platform-browser` provides an * platforms that Angular supports. For example, `@angular/platform-browser` provides an
* implementation specific to the browser environment, while `@angular/platform-webworker` provides * implementation specific to the browser environment, while `@angular/platform-server` provides
* one suitable for use with web workers. * one suitable for use with server-side rendering.
* *
* The `PlatformLocation` class is used directly by all implementations of {@link LocationStrategy} * The `PlatformLocation` class is used directly by all implementations of {@link LocationStrategy}
* when they need to interact with the DOM apis like pushState, popState, etc... * when they need to interact with the DOM APIs like pushState, popState, etc.
* *
* {@link LocationStrategy} in turn is used by the {@link Location} service which is used directly * {@link LocationStrategy} in turn is used by the {@link Location} service which is used directly
* by the {@link Router} in order to navigate between routes. Since all interactions between {@link * by the {@link Router} in order to navigate between routes. Since all interactions between {@link
* Router} / * Router} /
* {@link Location} / {@link LocationStrategy} and DOM apis flow through the `PlatformLocation` * {@link Location} / {@link LocationStrategy} and DOM APIs flow through the `PlatformLocation`
* class they are all platform independent. * class, they are all platform-agnostic.
* *
* @publicApi * @publicApi
*/ */