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(forms): Property renaming safe code #45271
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). For more information, open the CLA check for this pull request. |
Is there a corresponding issue for this PR? This is pretty surprising behavior if true -- would love to check out a repro. EDIT: context is in b/222494799. This was escalated internally. There are some test failures -- I'm working with Ananya on chat to resolve them. |
Thank you for your PR. I've left a few comments. You'll also want to rerun the formatter -- check the lint
CI result for instructions.
Looks great! Just a few last things before this can be merged:
|
This fixes property renaming related issues in advanced closure compiler optimizations.
@ananyahs96 We're waiting on one more approval for |
I am ready to merge. Thanks Dylan! |
This PR was merged into the repository by commit aa7b857. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This fixes property renaming related issues in advanced closure compiler optimizations. PR Close angular#45271
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
It was causing ng-touched not to be applied in optimized mode/prod where the compiler runs the full set of optimizations and compiler checks. This behavior is likely the case with all other ng control statuses.
Issue Number: N/A
What is the new behavior?
ng-touched is now applied successfully in all javascript compilation modes.
Does this PR introduce a breaking change?
Other information