[Fedor Losev]

The type information is lost so there is no autocomplete and no validation.

E.g. for *ngIf="x$ | async; let x" or for *ngIf="x$ | async; let x: T" the x itself is available in autocomplete and validated, but it has no type. So there is no autocomplete for x. and x.invalidmember passes validation.

This is super important feature as ngif and ngfor variables were introduced to get rid of subscriptions or multiple async, but without autocomplete and validation they are hard and dangerous to work with.

Another related problem: https://www.genuitec.com/forums/topic/no-type-in-ngfor-for-iterable-interface-in-template-validator-autocomplete/

[support-swapna]

Fedor,

Thank you for raising it. I could replicate the problem at my end and a bug is filed for the dev team.
We will let you know when the fix is out.

–Swapna
MyEclipse Support

[Author]

Posts