Matthieu Riegler

Fwiw this can be reproduced also with an `@if` block. @let testType = test.type; @if(testType == 'a') { {{test.name}} // errror }

So it looks like this one might me be somehow a typescript issue (a bit like #59215). The TCB generates something like this ``` function _tcb1(this: { test: Test })...

I might need to defer to @JoostK (who is so much more knowledgable on that topic) for this question.

The TS issue was closed with a merged PR. We'll have to wait the next TS release to see if the issue is indeed fixed.

Closely related is #14545 (and #43485 as a more canonical one). Support for class/style bindings is more straightforward than for inputs/outputs (see the [generated instructions](https://jeanmeche.github.io/angular-compiler-output/?template=PGRpdiBbY2xhc3NdPSJ7ICdwdC0xNic6IG5iIH0iPjwvxIF2Pgo%3D)), but the question is more...

Without the check that joost mentions, `{ ...css }` would create a new object everytime CD runs (= every time the template function runs).

Hi, this PR seems to be a duplictate of #51951 were this change has been discussed.

TLDR of the issues mentionned by Pawel: the class/style bindings do not cover all the cases covered by ngClass/ngStyle directives. It's actually a reason why we dediced to not deprecate...

Yeah we should have that information somewhere, probably in the guides. We even have an issue for that #40623.

We've landed an ngClass migration with #62983. It'll be available in v21.