-
-
Notifications
You must be signed in to change notification settings - Fork 134
Rich and Markdown Text Editor #2501
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
base: master
Are you sure you want to change the base?
Conversation
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
… SN theme, formik bridge touchups, a better toolbar style
…gic, image markdown transformer, testing on more scenarios
…ty; re-instate SN markdown renderer
…cussions create/edit
…s for markdown mode
…t, re-introduce usage of Lexical in read mode
…ustomAutoLink plugin
…ia component rendering
…fore lexical loads
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
- Helper floating toolbar on selection - graceful appear/disappear of the toolbar - debounce reposition to check if the selection actually didn't change - reposition tolerance - Show a tooltip on toolbar item hover - ActionTooltip now accepts delay, transitions and a different structure - Show a tooltip after 0.5 seconds - graceful transition - hide the tooltip on click
- prevent importing an empty editor state - adjust code nodes theme for dark and light mode - hide floating elements far away from the viewport - tweaks to floating elements animations - fix overflow and overflowing button on Reader and Reader loading placeholder - accept and use a callback ref for LexicalReader and a normal ref for (markdown) Text bits: - split SNLexical in LexicalEditor and LexicalReader - forward ref to loading placeholder and Reader
…ers on dynamic Editor import; fix newlines on SSR markdown conversions
…down]; save pure lexical state in local; start in markdown mode by default
… changes for markdown mode
…upport; overflow at 50vh for truncated HTML; prepare for imgproxy support
…ort via applySNCustomizations, embed HTML placeholder
- safer SSR conversions, withDOM wrapper - rename blockType normal to paragraph - migrate LexicalReader to the new extension paradigm - change math nodes placeholder - refactor: re-organize lib/lexical in functionalities [core, content, decorative, formatting, misc] - refactor: re-organize components/lexical in functionalities - MaxLength plugin for constrained text boxes
…HTML placeholder; mitigate: corrupt selection switching between markdown and rich modes; dev: debug HTML mode; State of Lexical docs
Description
Introduces Lexical as a Markdown/Rich Text editor and renderer
Screenshots
tbd
New things
4kB
of size in the bundle (this has to be re-verified later)MediaOrLink
preserves scroll on load, supports captions and resizeAdditional Context
Lexical is also used as a renderer (stripped of any plugins) of its
editorState
in JSON.Since Lexical renders client-side, the HTML produced by Lexical is used as a placeholder with 1:1 styling until Lexical takes over
TBD, a lot has changed from the last update
Progress
TODO
TBD, a lot has changed from the last update*
Checklist
Are your changes backward compatible? Please answer below:
For example, a change is not backward compatible if you removed a GraphQL field or dropped a database column.
tbd
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
tbd
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
tbd
Did you introduce any new environment variables? If so, call them out explicitly here:
tbd
Did you use AI for this? If so, how much did it assist you?
Ask: better lexical understanding, things that weren't clear in documentation or in code, best practices
Agent: autocompletion and refactors