-
Notifications
You must be signed in to change notification settings - Fork 26.2k
docs: add update instructions for v20 #61338
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
base: main
Are you sure you want to change the base?
Conversation
Deployed adev-preview for 2873e6c to: https://ng-dev-previews-fw--pr-angular-angular-61338-adev-prev-vc9ib7ze.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
5fc3515
to
2873e6c
Compare
"If your templates use `{{ in }}` or `in` in expressions to refer to a component property named 'in', change it to `{{ this.in }}` or `this.in` as 'in' now refers to the JavaScript 'in' operator.", | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2nd thoughts of this. This solution isn't enough when in
is a template reference. It's one of the cases I had to fix in g3. In that case, the in
reference had to be renamed. Would we also want to mention that alternative ?
No description provided.