-
Notifications
You must be signed in to change notification settings - Fork 6
Retrieve editor contents/Expose quill instance #9
Comments
Good point. I think that since the idea behind the widget is simplicity and drop-in functionality, we should maintain encapsulation around Quill. For the purpose of retrieving editor contents, it may make more sense to expose a reference (or wrapper interface) to the GoInstant OT api, rather than to Quill, since OT is the data layer. One option would be to add a Then the only decision would be if we want to rely on the client instantiating their own OT key (using What do you think? |
This fixes #9. Signed-off-by: byronm <byronm@cs.stanford.edu>
This fixes #9. Signed-off-by: Jason Chen <jhchen7@gmail.com>
This fixes #9. Signed-off-by: byronm <byronm@cs.stanford.edu> Signed-off-by: Jason Chen <jhchen7@gmail.com>
Doesn't look like there's a publicly exposed method for retrieve the editor contents programatically.
Since the widget is built on top of Quill, which does expose this functionality, perhaps the internal Quill instance should just be exposed publicly and documented?
Alternatively there could be interfaces that call through to the Quill instance if you don't want to expose that for encapsulation reasons.
The text was updated successfully, but these errors were encountered: