Prevent y-websocket initial value from entering slate-history undos about slate-yjs HOT 3 CLOSED

@BitPhinix, thank you. That was an excellent suggestion and worked beautifully.

I can't think of a good reason why one would want remote changes to creep into their local history. I wish there was an easy way to add this to slate-jys, but it feels wrong to require slate-history in slate-yjs even though I bet a large majority of people using slate-yjs use slate-history as well. Below is the code I added after creating the editor for anyone else who is interested:

  const { apply } = editor
  editor.apply = (...args) => {
    if (YjsEditor.isRemote(editor)) {
      HistoryEditor.withoutSaving(editor, () => {
        apply.apply(editor, args)
      })
    } else {
      apply.apply(editor, args)
    }
  }

from slate-yjs.

Hi @SamDuvall,

Another way you could solve this is by wrapping editor.apply with a handler that checks if YjsEditor.isRemote(editor) is true and then wrapping the next call with HistoryEditor.withoutSaving

I haven't actually tested it, but it should work 😄

from slate-yjs.

Awesome, glad I could help!

I haven't yet added this to slate-yjs because I'm planning to add another history handling plugin based on Y.UndoManager to have proper Yjs history support. I'm really busy at the moment but will get back to it in the coming months

from slate-yjs.