feat(Lexical): HTML to lexical parser #3569
Merged
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
mihajlovco
changed the title
mihajlovco
changed the title
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.
This PR introduce a new package,
lexical-converter, which supports:This feature will allow the users to convert their HTML content to a Lexical editor state and import the editor state into our PB and HCMS apps.
Both the HTML parser and state transformer rely on the headless Lexical editor. This not only keeps the transformation consistent in all directions, but also allows you to configure the tool with your own Lexical nodes which you might need, and which you might already be using in the Webiny Admin app.
How Has This Been Tested?
Jest tests.
Documentation
To see the usage as well as advanced mapping examples, consult the test files in the package.