Alex Rickabaugh

Tracking as [FW-2197](https://angular-team.atlassian.net/browse/FW-2197) internally.

I see the fact that Ivy doesn't complain (without `fullTemplateTypeCheck` mode) as a bug. We should match View Engine's behavior, and that means running the unknown element checks even in...

I wonder if this is something we can fix in the type definitions for `NgSwitch`, with the tools we have today. Or if this is going to require some special...

This is a big challenge, mainly as it's a design limitation with how `NgSwitch` works. I think we should look into ways of doing this, but realistically I don't think...

This PR was merged into the repository by commit 19d7fb08a31d46a79bec6f4a6f3a3b73bca0c8dc.

This PR was merged into the repository by commit 75df4044675c61d2b646437cfe64fe828a39b3a0.

This PR was merged into the repository by commit 54ceed53e21a6a899617b626becc51ffb1059178.

Closing as the issue is related to having multiple copies of Angular at runtime due to the build structure. Please feel free to open an issue with a reproduction if...

I'm going to close this issue as a duplicate of #15280 - fundamentally this is asking for template local variables (as evidenced by the suggestions of `*ngrxLet` above.

This PR was merged into the repository by commit 50378d0eb95349446fce122022fc596030ff0415.