Closed palant closed 3 weeks ago
Name | Link |
---|---|
Latest commit | 1a2085c7174bc2be90ef5637a590e25d6055ebf8 |
Latest deploy log | https://app.netlify.com/sites/elk-docs/deploys/6718048c0a22ce0008698bb4 |
Name | Link |
---|---|
Latest commit | 1a2085c7174bc2be90ef5637a590e25d6055ebf8 |
Latest deploy log | https://app.netlify.com/sites/elk-zone/deploys/6718048c35111f00081c11d6 |
Deploy Preview | https://deploy-preview-3014--elk-zone.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Thank you for the detailed analysis! I can also confirm the fix with the reproduction steps. 💯
Steps to reproduce are in https://github.com/elk-zone/elk/issues/2216#issuecomment-2424229983. This fixes #2216 and #2889.
The issue here is function
groupItems
issuing identical IDs for different objects. In the first update it creates aGroupedLikeNotifications
instance with IDgrouped-0
. Then we get a second update, and it again creates aGroupedLikeNotifications
instance with IDgrouped-0
. Since both have the same key, Vue attempts to reuse the existing node for the new object. It replaces the existingvnode
inStatusBody
by one that belongs to a different status, and it fails miserably updating the display. So we get a correct internal structure but a completely messed up display. The solution is using a global ID counter, so that this function never re-issues the same ID.