Need help with lexical -> markdown

[cobalt quail]

Where exactly do we do the transformation for lexical -> markdown.

1. Should I create richtext field with json and then update a separate field for markdown?

https://payloadcms.com/docs/rich-text/lexical#lexical-markdown - Where exactly is this transformer used?

[frozen turret]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• lexical-markdown
• markdown-lexical
• redirects-plugin
• seo-plugin
• nested-docs-plugin

Community-Help:

• How can I create a table?

[cobalt quail]

@reef spoke ^

[reef spoke]

Where exactly do we do the transformation for lexical -> markdown.
You decide! Wherever you want. You can run the code snippet for transforming => markdown anywhere.

If you want it outputted as a field, alongside the normal editor field, you could create a new field, add an afterRead hook to it, and then run the markdown transformation within that afterRead hook

[cloud skiff]

Hi, Alessio.

So I've crafted this code, but it seems that EditorState is null, so it throws an error during build. Can you please point out what's wrong with implementation?

Here is implementation and error - https://gist.github.com/yevarizhko/a7232170bd0f168c8a2655e787bc5d09

[reef spoke]

Hey! EditorState is undefined because you are defining a new variable let yourEditorState without initializing it. If you don't initialize a new variable it's undefined, which is is why you're getting Cannot read properties of undefined (reading 'root')

You probably want to initialize it with value which you get from your afterRead hook

So I would move the entire logic of creating and initializing the headless editor into your afterRead hook