Description
In lexical, there is a MarkNode that allows you to store the comment ID relative to the selected text fragment. This functionality can be extended to demonstrate, in the playground, a type of comment with suggested changes. A comment in “suggest” mode should store the comment text and the suggested text that replaces the selected fragment. In the simplest implementation, it is sufficient to store plain text, but an excellent option is to save and apply rich text in the two formats supported by lexical: JSON and HTML.
It would also be good to expand the agent-example shown on the home page https://lexical.dev and add a comment suggestion feature with LLM integration
Google Docs and TipTap can be used as references
Impact
This popular feature in rich WYSIWYG editors will highlight the extensive capabilities of Lexical and facilitate integration
Description
In lexical, there is a MarkNode that allows you to store the comment ID relative to the selected text fragment. This functionality can be extended to demonstrate, in the playground, a type of comment with suggested changes. A comment in “suggest” mode should store the comment text and the suggested text that replaces the selected fragment. In the simplest implementation, it is sufficient to store plain text, but an excellent option is to save and apply rich text in the two formats supported by lexical: JSON and HTML.
It would also be good to expand the agent-example shown on the home page https://lexical.dev and add a comment suggestion feature with LLM integration
Google Docs and TipTap can be used as references
Impact
This popular feature in rich WYSIWYG editors will highlight the extensive capabilities of Lexical and facilitate integration