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
Documentation for ng-for #4533
Documentation for ng-for #4533
Conversation
* out, and unchanged rows retain any unsaved state such as user input. | ||
* | ||
* If the entire iterator is replaced, Angular will tear down the entire DOM and rebuild it with | ||
* from the new iterator, even if none of the elements have changed. This is an expensive |
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.
with from --> with / from
* reproduce those changes in the DOM. New rows can be animated in, removed rows can be animated | ||
* out, and unchanged rows retain any unsaved state such as user input. | ||
* | ||
* If the entire iterator is replaced, Angular will tear down the entire DOM and rebuild it with |
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.
Are you sure this is the case? If so, we actually need to change it, so it is not the case.
Merging PR #4533 on behalf of @alxhub to branch presubmit-alxhub-pr-4533. |
User @naomiblack does not have PR merging privileges. |
@alxhub please clang-reformat and merge |
Merging PR #4533 on behalf of @IgorMinar to branch presubmit-IgorMinar-pr-4533. |
* # Change Propagation | ||
* | ||
* There are two reasons why `NgFor` will need to update the DOM: | ||
* * The contents of the iterator changes. |
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.
contents --> content
or
changes --> change
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. |
No description provided.