Open ViktorZhurbin opened 1 month ago
One approach would be updating quill.keyboard.options
directly so in binding handlers, you could read the options dynamically
One approach would be updating
quill.keyboard.options
directly so in binding handlers, you could read the options dynamically
Typescript would not be happy about it. There's probably a reason for this property to be protected:
Property 'options' is protected and only accessible within class 'Module<T>' and its subclasses
I opened #4237 which seems like a separate bug to me. I wouldn't hit it, if I didn't have to re-create the editor. But it's still a bug on its own.
Question: Do I have to create a new Quill instance to update
modules
? Or is there a way to update them directly, something like:Context: I need to override some default keyboard bindings, and I do it through the config as suggested. When a binding needs to be updated (eg, user can change it in settings), it looks like I need to create a new Quill instance with updated config. This creates an extra hustle of saving/re-applying existing user input and selection.