Extending mdx-editor / lexical editor

[jannikbuschke]

I am wondering what the general philosophy here is. Is it possible to apply lexical knowledge to extend mdx-editor, or can this only be done via the Gurx state manangement thing?

https://mdxeditor.dev/editor/docs/extending-the-editor

What would need to be done to use a lexical plugin? Is it possible or would one need to reimplement it with an "mdx editor plugin"?

[petyosi]

Lexical knowledge is a must if you want to build custom editors, for example. For other things (like support of new syntax), you need understanding of the mdast specifics.

Pure lexical plugins can be integrated. For example, I'm using the MarkdownShortcutsPlugin like this. However, a Lexical plugin "plugin" system is usually just a component that does a bunch of stuff with the editor in useEffect. It's hard to make composition / reusability of state like this, as it will usually lead to a mess of spaghetti hooks and context. That's why I came up with the Gurx patterns.

Hope this makes sense.

[noteverseio]

Yes, the MDXEditor can be highly extensible and easily integrated with Lexical Plugin, I have tried floating toolbar, slash command, collaboration, autocomplete etc from lexical playground into my editor, all working fine so far.

[jannikbuschke]

@noteverseio can you give some example code of a collaboration setup?
I somehow cannot get it to work

[NehalDamania]

llaboration, autocomplete etc from lexical playground into my editor, all working

@noteverseio I am trying to implement @mentions and #hashtags autocomplete. Any examples or suggestions of autocomplete would be greatly appreciated.

[rob-at-airwalk]

does this help anyone? it works for me, but would be good to get a better view on it...
#535

[rob-at-airwalk]

@noteverseio, did you get collaboration working with tables ? any examples without forking this repo ?