Operations

operations are the granular, low level actions that occur while invoking transforms a single transform could result in many low level operations being applied to the editor slate's core defines all of the possible operations that can occur on a richtext document for example editor apply({ type 'insert text', path \[0, 0], offset 15, text 'a new string of text to be inserted ', }) editor apply({ type 'remove node', path \[0, 0], node { text 'a line of text!', }, }) editor apply({ type 'set selection', properties { anchor { path \[0, 0], offset 0 }, }, newproperties { anchor { path \[0, 0], offset 15 }, }, }) under the covers slate converts complex transforms into the low level operations and applies them to the editor automatically so you rarely have to think about operations unless you're implementing collaborative editing 🤖 slate's editing behaviors being defined as operations is what makes things like collaborative editing possible, because each change is easily define able, apply able, compose able and even undo able!