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
I have found out the list plugin is not supported in NestedLexicalEditor, this can be easily reproduced in live demo where you can insert a tip/warning directive or any other directives that use NestedLexicalEditor, then applying a numbered, bullet or check list in the nested editor won't have any effect.
Is this the expected behavior that nested editor only supports limited markdown syntax?
The text was updated successfully, but these errors were encountered:
Besides, the changes in nested editor are not always reflected in the parent markdown content as I switched to the markdown source view and the changes in nested editor were not applied to the markdown content.
Thanks for catching that, I just pushed a fix for the problem. It's a lexical "ceremony", some features need to be registered explicitly for the nested editors. This gives some flexibility, but also imposes extra work.
Re: the change problem. There's another issue open on the matters, still thinking of how to handle it correctly.
Hey dear mdxeditor authors:
I have found out the list plugin is not supported in NestedLexicalEditor, this can be easily reproduced in live demo where you can insert a tip/warning directive or any other directives that use NestedLexicalEditor, then applying a numbered, bullet or check list in the nested editor won't have any effect.
Is this the expected behavior that nested editor only supports limited markdown syntax?
The text was updated successfully, but these errors were encountered: