-
Notifications
You must be signed in to change notification settings - Fork 87
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
Use setContent for collision resolution #233
Labels
Comments
@max-nextcloud This would be interesting to reevaluate with the ongoing y.js work if we can resolve the manual file overwrite outside of text more nicely by applying the new document on top of the existing editing session. |
Just talked about this with @juliushaertl. Some points to note:
|
Was done with 7512ef2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since tiptap 1.23.2 setContent will dispatch a transaction, so we could preserve the collaboration history with that even when we apply changes from the file from outside:
https://github.com/scrumpy/tiptap/releases/tag/tiptap%401.23.2
The text was updated successfully, but these errors were encountered: