add modifyStorage api to Node

[jrowny]

• Adds a new modifyDocumentStorage method to node client

Requires backend modification

Use it like this:

import { Liveblocks } from "@liveblocks/node";

const liveblocks = new Liveblocks({ secret:  "sk_dev_.....",});

await liveblocks.modifyStorageDocument("roomId", (root) => {
  const obj = root.get("someObject");
  obj.set("99", 12345);
});

Root will be a fully hydrated LiveObject.

With types:

type MyRoomStorage =  {
    someObject: LiveObject<{
      [key: string]: number | LiveObject<{ a: number }>;
    }>
}
await liveblocks.modifyStorageDocument<MyRoomStorage>("roomId", (root) => {
  const obj = root.get("someObject");
  obj.set("99", 12345);
});

[nvie]

Conceptually, I love this! The flow is so easy to follow:

• Download the full storage document
• Mutate it
• Discard the results
• Todo: error if an error happened on the server

See my code review comments on the server side. I think we'll need to figure out how to best define the concept of a "server session". I think the current "si" prefix we use to initialize a room from the REST API should become just a special case of whatever server session abstraction we land on.

Amazing work! 🙌

[nvie]

For server side room initialization, we use "si" as the prefix.

[nvie]

I'd like to expose a proper API for this right from the core package, to create a new client-side Storage context and initialize it from a stream of IdTuple<SerializedCrdt> values, rather than exposing the ManagedPool / CRDT internals here. But conceptually this is really great! 👌