Closed Sinsho closed 2 weeks ago
Might the problem be that the sync command only syncs the ydoc in make_ydoc (loaded from the database) with the ydoc in the room and therefore doesn't have the changes from User A?
Difficult to say without a reproducible example.
Is this intended behavior and if so is there some way in pycrdt-websocket to also force the ydoc in the room to get synced with the ydoc from the connecting user?
No it's not the intended behavior, all connected users should be in sync.
I can't reproduce it on the current state of our project. The documents correctly get synced now on reconnection.
Therefore, I assume it was an error on our end. Thanks for the fast reply!
Description
I'm using pycrdt-websocket in a Django application as a django channel consumer and y-websocket in a Vue application in the frontend as the client. The text editor used is Quill.
Up on connection from the client to the websocket I load the ydoc from the database in the overwritten method make_ydoc, then it gets synced (base behavior of the YjsConsumer).
Now I have following scenario:
Might the problem be that the sync command only syncs the ydoc in make_ydoc (loaded from the database) with the ydoc in the room and therefore doesn't have the changes from User A?
Is this intended behavior and if so is there some way in pycrdt-websocket to also force the ydoc in the room to get synced with the ydoc from the connecting user?