-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it compatible with @editorjs/list #15
Comments
I'm not involved in development, but .. what is "compatible with"? You're suggesting a code change, but I don't understand the advantage of the code change. |
The key is the difference between @editorjs/list and editor-js/nested-list. |
Well that sounds pretty useful. |
As described in #75 (comment), I take issue with this approach, and would urge to keep in mind other usages of editor.js documents than just editor.js itself. One clear advantage of a block-based format over plain (sanitized, white-listed) HTML, and indeed the reason we went for a block-based format, is that the data format is well-known and fairly limited, making it easier for other tools than editor.js itself to parse the content and format it for other contexts. For example, our back-end converts editor.js documents for display in Excel cells (plain-text with simple "formatting" such as prepending bullet points with This parsing becomes much more difficult if, for any given My proposal would be to use another |
update Line 106 in the
constructor
:The text was updated successfully, but these errors were encountered: