Value changes many time in instantly when using the multiple move method of LiveList quickly

[jiwon79]

Value changes many time in instantly when using the multiple move method of LiveList quickly

[GuillaumeSalles]

Hi @jiwon79,

First of all, thank you for the detailed bug report and patience.

Liveblocks packages and packages version
@liveblocks/[email protected]
@liveblocks/[email protected]

I believe this issue is also present on the latest version, but can you confirm you see the same behavior after upgrading? We recommend having the same version for both @liveblocks/react and @liveblocks/client.

Unfortunately, we have a few LiveList issues including that one that requires a deeper refactoring to be able to fix them properly. We have plans to do that, but not in the short term. Could you explain what is your use case and why consecutive move are frequently done in your product? Maybe there is a workaround that we can help you find

[enk0de]

Hi! Thank you for response. I am on the same team with @jiwon79

---

We recommend having the same version for both @liveblocks/react and @liveblocks/client.

A: We are already using same version for @liveblocks/react, @liveblocks/client.

Why consecutive move are frequently done in your product

A: We are creating a Figma-like Design Tool. We have a "Stack" feature, in which user can move index element in Stack. Then when user moving element index in Stack quite fastly, blinking issue appears.

---

Did you know that there are also serious history management issues? History Undo/Redo doesn't work well. If you go back to the days before history.undo() immediately after creating an item, all history records will be deleted, or you can use the History. This problem occurs in liveblocks official demo page too (https://liveblocks.io/document/storage)

[enk0de]

i found that the logic at case of ServerMsgCode.UPDATE_STORAGE in room.ts_handleServerMessage causes the local state to mutate. Shouldn't updates be ignored If both remote event trigger source and the client are same? (updating storage is initiated by the client itself)

          case ServerMsgCode.UPDATE_STORAGE: {
            const applyResult = applyOps(message.ops, false);
            for (const [key, value] of applyResult.updates.storageUpdates) {
              updates.storageUpdates.set(
                key,
                mergeStorageUpdates(updates.storageUpdates.get(key), value)
              );
            }
            break;
          }