Component Switch to Lexical #14
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
…xample, will remove in the future to be replace by react-icons
…ted it to a react component for onChange to work with my react forms
…entially send an empty string as a tag
…the lexical rich text editor by facebook.
…red as json, started figuring out a way to properly display that data while retaining the styling.
…y set inner html, fixed the styling for the text as well
…working as it should
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.
Decided to use a rich text editor called Lexical for creating recipes instead of the custom solution I originally made. This should Improve performance, and let recipes look better while also giving users more control over what they're doing.