Improved Grammar under Setting Up Animation (#28608)
From "...must include into the root module's imports array." to "...must be included into the root module's imports array."
This commit is contained in:
@ -20,9 +20,9 @@ Angular animations is the framework's streamlined version of what CSS natively p
|
||||
|
||||
#### Setting up Animations
|
||||
|
||||
Before animating, the `BrowserAnimationsModule` must include into the root module’s imports array. It is available from `@angular/platform-browser/animations`. This NgModule ensures animations work for the given platform. This article assumes the standard web browser for each example.
|
||||
Before animating, the `BrowserAnimationsModule` must be included into the root module’s imports array. It is available from `@angular/platform-browser/animations`. This NgModule ensures animations work for the given platform. This article assumes the standard web browser for each example.
|
||||
|
||||
Angular animations declare within the `@Component` metadata. `@Component` decorates a class to distinguish it as a component to Angular. Its metadata contains component configurations including the `animations: []` field. Each array element from this field represents an animation trigger (`AnimationTriggerMetadata`).
|
||||
Angular animations declare within the `@Component` metadata. `@Component` decorates a class to distinguish it as a component to Angular. Its metadata contains component configurations including the `animations: []` field. Each array element from this field represents an animation trigger (`AnimationTriggerMetadata`)
|
||||
|
||||
Animations are exclusive to their host component via the decorator's metadata. Animations can only be used in the host component’s template. Animations do not inherit to the component's children. There is an easy work-around for this.
|
||||
|
||||
|
Reference in New Issue
Block a user