You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first saw QuillRawEditor, I thought it would be a lower-level abstraction than QuillEditor, with QuillEditor depending on it. I expected QuillRawEditor to have fewer features but offer more control and extensibility, requiring more manual implementation. However, I'm not sure if this is the case, as most features we're working on are being implemented in QuillRawEditorState.
A low level means you're closer to the core, having more access at the price of handling more things yourself.
So if anyone knows why it's separated (in detail), I'd appreciate any feedback, If there isn't a strong reason, we may consider a different approach in the long term.
If there as a strong reason, we should document it.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
The question
When I first saw
QuillRawEditor
, I thought it would be a lower-level abstraction thanQuillEditor
, withQuillEditor
depending on it. I expectedQuillRawEditor
to have fewer features but offer more control and extensibility, requiring more manual implementation. However, I'm not sure if this is the case, as most features we're working on are being implemented inQuillRawEditorState
.A low level means you're closer to the core, having more access at the price of handling more things yourself.
So if anyone knows why it's separated (in detail), I'd appreciate any feedback, If there isn't a strong reason, we may consider a different approach in the long term.
If there as a strong reason, we should document it.
The text was updated successfully, but these errors were encountered: