ng-for and ng-if break with transformer generated change detectors

[jakemac53]

#2981 provides a test which fails. https://gist.github.com/jakemac53/675fdedad5ce469d292f is an simple example which will fail under the transformer.

[vsavkin]

The actual issue:

The DOM adapter used by the compiler used in the DirectiveProcessor transformer incorrectly reflects on the elements. The adapter cannot detect properly what properties a DOM element has. This problem manifests via change detection.

[matanlurey]

Is anyone tackling this? @tbosch mentioned something about registering a Schema last week.

[vsavkin]

@matanlurey we'll figure out a plan today. It looks like providing a schema would be a proper solution, but it may take some time. We may have to provide a temporary solution to unblock @jakemac53.

[yjbanov]

Assigned to @tbosch as he is already looking into the reflection issue.

[tbosch]

Have a PR up, should go in today.

[kevmoo]

Verified on 97ef1c2 with Dartium. Awesome! 🤘

[matanlurey]

👍 looks good thanks guys.

[jakemac53]

todomvc works with the transformer now as well :)

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}