Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(compiler-cli): incorrectly interpreting $any calls with a property read #44657

Closed
wants to merge 1 commit into from

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jan 7, 2022

This was flagged during the code review of #44580. When generating a type check block, we were interpreting any call to $any as an as any cast, even if it's part of a PropertyRead (e.g. foo.$any(1)). This is handled correctly in other parts of the compiler, but it looks like it was missed in the type checker.

…y read

This was flagged during the code review of angular#44580. When generating a type check block, we were interpreting any call to `$any` as an `as any` cast, even if it's part of a `PropertyRead` (e.g. `foo.$any(1)`). This is handled correctly in other parts of the compiler, but it looks like it was missed in the type checker.
@crisbeto crisbeto marked this pull request as ready for review Jan 7, 2022
@pullapprove pullapprove bot requested a review from atscott Jan 7, 2022
@ngbot ngbot bot added this to the Backlog milestone Jan 7, 2022
@ngbot ngbot bot added this to the Backlog milestone Jan 7, 2022
atscott
atscott approved these changes Jan 7, 2022
Copy link
Contributor

@atscott atscott left a comment

👍

@atscott
Copy link
Contributor

@atscott atscott commented Jan 7, 2022

This PR was merged into the repository by commit eeaabe7.

atscott added a commit that referenced this issue Jan 7, 2022
…y read (#44657)

This was flagged during the code review of #44580. When generating a type check block, we were interpreting any call to `$any` as an `as any` cast, even if it's part of a `PropertyRead` (e.g. `foo.$any(1)`). This is handled correctly in other parts of the compiler, but it looks like it was missed in the type checker.

PR Close #44657
amitbeck added a commit to amitbeck/angular that referenced this issue Jan 13, 2022
…y read (angular#44657)

This was flagged during the code review of angular#44580. When generating a type check block, we were interpreting any call to `$any` as an `as any` cast, even if it's part of a `PropertyRead` (e.g. `foo.$any(1)`). This is handled correctly in other parts of the compiler, but it looks like it was missed in the type checker.

PR Close angular#44657
@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Feb 7, 2022

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants