You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<div *ngFor="let item of items">
<div>{{ item.name}} {{item.surname}}</div>
</div>
I have a component which lists all the objects of a certain kind and every time time a new object of that kind gets created I want it to show an :entry web-animation on that item.
Everything's fine, until you start using Optimistic UI. With Optimistic UI a new object gets created with a random ID and some presumed-to-be data. The animation immediately starts (we don't have to wait for the server's rensponse), but way before it is supposed to finish that object gets destroyed, because a new immutable object has been binded.
If the user could opt-in for mutable changes for Optimistic UI to real data transitions, that issue wouldn't occur because ngFor is smart enough to do diffes to actually remove only the DOM nodes that are in need to.
The text was updated successfully, but these errors were encountered:
Use case:
I have a component which lists all the objects of a certain kind and every time time a new object of that kind gets created I want it to show an
:entry
web-animation on that item.Everything's fine, until you start using Optimistic UI. With Optimistic UI a new object gets created with a random ID and some presumed-to-be data. The animation immediately starts (we don't have to wait for the server's rensponse), but way before it is supposed to finish that object gets destroyed, because a new immutable object has been binded.
If the user could opt-in for mutable changes for Optimistic UI to real data transitions, that issue wouldn't occur because ngFor is smart enough to do diffes to actually remove only the DOM nodes that are in need to.
The text was updated successfully, but these errors were encountered: