feat(richtext-lexical): mdx support #7993
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cal markdown transformers
…dth, and lexical blocks field hover / click effects not working as intended
…an the editor width.
…ures, like the ClientField
…as they cause the editor to overflow without it resizing
…now, to add multiline markdown import tag counting for proper matching
…multiline transformers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Supports bi-directional import/export between MDX <=> Lexical. JSX will be mapped to lexical blocks back and forth.
This will allow editing our mdx docs within payload while keeping mdx as the source of truth