Skip to content
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

Support CRDT rich text #236

Open
steida opened this issue Oct 21, 2023 · 3 comments
Open

Support CRDT rich text #236

steida opened this issue Oct 21, 2023 · 3 comments

Comments

@steida
Copy link
Contributor

steida commented Oct 21, 2023

Based on my Peritext PoC.

@negue
Copy link
Collaborator

negue commented Mar 1, 2024

Rich Text would be HTML?

or would markdown itself be considered as rich text and with that could result in issues having that in a property ?

@steida
Copy link
Contributor Author

steida commented Mar 1, 2024

https://github.com/evoluhq/evolu.me uses Lexical data model. It works, but it could be better. You can store HTML as a string as well. Unfortunately, the ideal solution is much harder: something like Automerge + Peritext.

@steida
Copy link
Contributor Author

steida commented May 12, 2024

Automerge 2.2 supports Rich Text 🎉 But the automerge itself isn't working with Next.js.

automerge/automerge#925

The idea is to leverage Automerge in Evolu for rich tech documents and use Evolu as a sync encrypted, etc. layer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants