PR Close #22975
This commit is contained in:
Veres Lajos
2018-03-10 17:14:58 +00:00
committed by Matias Niemelä
parent f739f756ce
commit de90314304
62 changed files with 112 additions and 108 deletions

View File

@ -797,7 +797,7 @@ export interface Pipe {
*
* Normally pipe's `transform` method is only invoked when the inputs to pipe`s
* `transform` method change. If the pipe has internal state (it's result are
* dependant on state other than its arguments) than set `pure` to `false` so
* dependent on state other than its arguments) than set `pure` to `false` so
* that the pipe is invoked on each change-detection even if the arguments to the
* pipe do not change.
*/

View File

@ -41,7 +41,7 @@ export interface ObjectOrientedRenderer3 {
querySelector(selectors: string): RElement|null;
}
/** Returns wether the `renderer` is a `ProceduralRenderer3` */
/** Returns whether the `renderer` is a `ProceduralRenderer3` */
export function isProceduralRenderer(renderer: ProceduralRenderer3 | ObjectOrientedRenderer3):
renderer is ProceduralRenderer3 {
return !!((renderer as any).listen);

View File

@ -35,7 +35,7 @@ export interface TypeDecorator {
}
export const ANNOTATIONS = '__annotations__';
export const PARAMETERS = '__paramaters__';
export const PARAMETERS = '__parameters__';
export const PROP_METADATA = '__prop__metadata__';
/**

View File

@ -462,7 +462,7 @@ function updateProp(
// expected nodeIndex which a ngOnInit should be called. When sending
// ngAfterContentInit and ngAfterViewInit it is the expected count of
// ngAfterContentInit or ngAfterViewInit methods that have been called. This
// ensure that dispite being called recursively or after picking up after an
// ensure that despite being called recursively or after picking up after an
// exception, the ngAfterContentInit or ngAfterViewInit will be called on the
// correct nodes. Consider for example, the following (where E is an element
// and D is a directive)

View File

@ -36,7 +36,7 @@ function attachProjectedView(vcElementData: ElementData, view: ViewData) {
// - add a view to template._projectedViews only 1x throughout its lifetime,
// and remove it not until the view is destroyed.
// (hard, as when a parent view is attached/detached we would need to attach/detach all
// nested projected views as well, even accross component boundaries).
// nested projected views as well, even across component boundaries).
// - don't track the insertion order of views in the projected views array
// (hard, as when the views of the same template are inserted different view containers)
view.state |= ViewState.IsProjectedView;