@wmhilton 's suggestion and code snippet is good for most case.
However, Snapshot only works when gc is false. This means you cannot revert the changes when some deletions have merged in yjs (just like squash in Git). Using yjs as a partial library that helps collaboration instead of making yjs the fundamental core of the data structure like our app AFFiNE, the Snapshot is good.
I’m our app. We use another approach to revert selected data and work when GC is enabled.
export function revertUpdate(
doc: Doc,
snapshotUpdate: Uint8Array,
getMetadata: (key: string) => 'Text' | 'Map' | 'Array'
) {
const snapshotDoc = new Doc();
applyUpdate(snapshotDoc, snapshotUpdate, snapshotOrigin);
const currentStateVector = encodeStateVector(doc);
const snapshotStateVector = encodeStateVector(snapshotDoc);
const changesSinceSnapshotUpdate = encodeStateAsUpdate(
doc,
snapshotStateVector
);
const undoManager = new UndoManager(
[...snapshotDoc.share.keys()].map(key => {
const type = getMetadata(key);
if (type === 'Text') {
return snapshotDoc.getText(key);
} else if (type === 'Map') {
return snapshotDoc.getMap(key);
} else if (type === 'Array') {
return snapshotDoc.getArray(key);
}
throw new Error('Unknown type');
}),
{
trackedOrigins: new Set([snapshotOrigin]),
}
);
applyUpdate(snapshotDoc, changesSinceSnapshotUpdate, snapshotOrigin);
undoManager.undo();
const revertChangesSinceSnapshotUpdate = encodeStateAsUpdate(
snapshotDoc,
currentStateVector
);
applyUpdate(doc, revertChangesSinceSnapshotUpdate, snapshotOrigin);
}
getMetadata is the function that returns what the AbstractType should be. In the yjs, all yjs data will be AbstractType eventually, and it doesn’t store the real type of it (which makes me feel weird).
Also you can see our test case for it
describe('milestone', () => {
test('milestone', async () => {
const doc = new Doc();
const map = doc.getMap('map');
const array = doc.getArray('array');
map.set('1', 1);
array.push([1]);
await markMilestone('1', doc, 'test1');
const milestones = await getMilestones('1');
assertExists(milestones);
expect(milestones).toBeDefined();
expect(Object.keys(milestones).length).toBe(1);
expect(milestones.test1).toBeInstanceOf(Uint8Array);
const snapshot = new Doc();
applyUpdate(snapshot, milestones.test1);
{
const map = snapshot.getMap('map');
expect(map.get('1')).toBe(1);
}
map.set('1', 2);
{
const map = snapshot.getMap('map');
expect(map.get('1')).toBe(1);
}
revertUpdate(doc, milestones.test1, key =>
key === 'map' ? 'Map' : 'Array'
);
{
const map = doc.getMap('map');
expect(map.get('1')).toBe(1);
}
const fn = vi.fn(() => true);
doc.gcFilter = fn;
expect(fn).toBeCalledTimes(0);
for (let i = 0; i < 1e5; i++) {
map.set(`${i}`, i + 1);
}
for (let i = 0; i < 1e5; i++) {
map.delete(`${i}`);
}
for (let i = 0; i < 1e5; i++) {
map.set(`${i}`, i - 1);
}
expect(fn).toBeCalled();
const doc2 = new Doc();
applyUpdate(doc2, encodeStateAsUpdate(doc));
revertUpdate(doc2, milestones.test1, key =>
key === 'map' ? 'Map' : 'Array'
);
{
const map = doc2.getMap('map');
expect(map.get('1')).toBe(1);
}
});
});
Maybe we will publish our y-indexeddb provider that support revert the version and more metadata for each ydoc