crisbeto da42a7648a fix(ivy): node placed in incorrect order inside ngFor with ng-container (#32324) ...

Fixes an issue where Ivy incorrectly inserts items in the beginning of an `ngFor`, if the `ngFor` is set on an `ng-container`. The issue comes from the fact that we choose the `ng-container` comment node as the anchor point before which to insert the content, however the node might be after any of the nodes inside the container. These changes switch to picking out the first node inside of the container instead.

PR Close #32324

2019-09-05 18:08:48 -04:00

..

schematics

refactor(core): undecorated-classes-with-decorated-fields migration commits empty updates (#32391)

2019-08-30 12:46:01 -07:00

src

fix(ivy): node placed in incorrect order inside ngFor with ng-container (#32324)

2019-09-05 18:08:48 -04:00

test

fix(ivy): node placed in incorrect order inside ngFor with ng-container (#32324)

2019-09-05 18:08:48 -04:00

testing

refactor(ivy): update the compiler to emit $localize tags (#31609)

2019-08-30 12:53:26 -07:00

BUILD.bazel

refactor(ivy): remove i18nLocalize instruction (#31609)

2019-08-30 12:53:26 -07:00

index.ts

refactor: move angular source to /packages rather than modules/@angular

2017-03-08 16:29:27 -08:00

package.json

build(zone.js): update zone.js to 0.10.2 (#31975)

2019-08-16 09:56:41 -07:00

PACKAGE.md

docs: add package doc files (#26047)

2018-10-05 15:42:14 -07:00

public_api.ts

build: publish tree of files rather than FESMs (#18541)

2017-08-31 15:34:50 -07:00