fix(richtext-lexical): lexical-html export #9793
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
|
This was because we had decided not to re-export Lexical packages that we were not using in Payload at the moment. That may change in the future for other packages, and it definitely doesn't make sense for this one if we are recommending it in the documentation. The only observation is that we were planning to make a new Lexical -> HTML converter that does not require more than editorState. However, for the other direction (HTML -> Lexical), I don't see that we can improve much the |
|
🚀 This is included in version v3.6.0 |
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.
What?
@lexical-htmlis missing from thelexical-proxyexports.Why?
To allow
@lexical-htmlfunctionality to be used without needing to install the package separately.How?
Adds
@lexical-htmlto thelexical-proxyexports.Fixes #9792