FEAT: Add support for promises to custom RTE API
Question
What are you trying to add to GrapesJS? Support for richtext editors with promise based APIs.
Describe your feature request detailed
CKEditor5's Editor.create and Editor.destroy methods return a Promise that resolves when the editor has been fully created or destroyed. This causes an issue when destroying the editor (when you finish editing a component) because GrapesJS syncs the changes to the model before the Editor.destroy promise has resolved which causes CKEditor HTML to be written to the model.
As a workaround you can sync the content again after the promise has resolved but it would be cleaner if the API supported promises.
We could add this in a backward compatible way be checking if the return values of the RTE's enable and disable methods are thennable and, if so, wait for the promise to resolve before continuing.
Is this something GrapesJS would consider supporting?
Is there an alternative at the latest version? No
Is this related to an issue? https://github.com/artf/grapesjs/issues/1516 https://github.com/artf/grapesjs/issues/1236
Answers (2)
Yeah, makes sense, probably I'd try to check if it's possible to make enable/disable methods (from ComponentTextView) async by default without breaking stuff, but checking if are thennable is always an option.
This should be already possible.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #2189
[Question] How to add "Ordered/Unordered List" option in rte/custom block
Hi I'm trying to create an ordered list with grapesjs. I tried adding the following to the rte: And this works if my page is pre-filled wit...
Issue #3639
[Feature]: Improve UndoManager API
One thing i think would add great functionality is a more detailed history stack. U can get the undo stack and build a sort of history repo...
Issue #3608
FEAT: Disable Dragging
What are you trying to add to GrapesJS? I have implemented an alternative text editing component (not based on RTE). I want people to be ab...
Issue #3558
FEAT: Support Content-Security-Policy
To reduce the possible attack surface if the editor is used in "hostile" environments (e.g. in SaaS platforms) support for CSP is required....
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.