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
there is already a same question in this issue but havent been answered.
ps. i have already read the documentation , but as @bondarewicz said it is a bit indistinct
The text was updated successfully, but these errors were encountered:
It's not gonna be slow per se, but there's just not going to be reordering at all.
For example instead of moving 1, 2, 3 to 3, 2, 1 it would update 1 to be 3, and 3 to be 1. For deeper component hierarchies, these can be deeper (and potentially more expensive) updates. Keys are the only way React can know that something has moved rather than updated. This is not just important for performance, but also for correctness. In our example earlier local state of 1 would be preserved for 3, although conceptually these are different items. But if we used keys then local state would "move" together with the item.
#8410
there is already a same question in this issue but havent been answered.
ps. i have already read the documentation , but as @bondarewicz said it is a bit indistinct
The text was updated successfully, but these errors were encountered: