-
Notifications
You must be signed in to change notification settings - Fork 615
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
How to render Headless CMS Richtext Custom Lexical Node #4380
Comments
So far i have managed to at least display the saved data by using a custom renderer like this:
This way i have lost the form layout, though and the content is also not editable anymore. |
@bschulz87 Headless CMS has its own Lexical config: https://www.webiny.com/docs/headless-cms/extending/lexical-editor, which is only applied to CMS context. Page Builder has its own, etc. So you basically did everything right, but you need to import the Btw. |
Thank you @Pavel910. I now have added the Custom Nodes to LexicalEditorConfig from ""@webiny/app-headless-cms" and "@webiny/app-page-builder". It's still not showing up. I guess the nodes are fine since they show up when using the RichTextLexicalRenderer.
|
@bschulz87 you keep mentioning Also, if it's not a secret, can you share the code of your nodes? Thanks. |
Hello,
i've followed the documentation on how to extend the Lexical Editor and cannot figure out how make the CMS render saved custom nodes. Inserting, saving and publishing works and i also get the the Node as Lexical State from the GraphQL API. After a refresh the nodes content are fetched from graphql but are missing the Richtext Editor.
I'm aware of the lexical-converter mentioned in https://www.webiny.com/docs/core-development-concepts/extending-and-customizing/lexical-tools#custom-nodes but i cannot find an example on how to implement it for the LexicalEditorConfig.
Version of Webiny is v5.40.5
App.tsx
Content from the /manage CmsEntriesGetPage request the CMS does on page detail:
The text was updated successfully, but these errors were encountered: