You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the new approach to load a document state from the file content, we should consider adding a way to initialize an editing session lazy. This could be useful for various cases:
In a read only document we likely don't need to update as often -> can be a large impact on instances that share a lot of read only files that get accessed frequently
In rich workspaces we could only lock the file once someone actually starts editing
Collectives could rather use this instead of requiring to switch between different editor components
We'd probably need:
Have an API to fetch the document content or yjs state without creating a new session, maybe even fetch steps for read only sessions
Some less frequent polling/notify push could then be used to check if a user editing joins or some steps were pushed
Think about how a handover can work from the UX perspective
Think about how the session can be initialized in the frontend code base
The text was updated successfully, but these errors were encountered:
Given the new approach to load a document state from the file content, we should consider adding a way to initialize an editing session lazy. This could be useful for various cases:
We'd probably need:
The text was updated successfully, but these errors were encountered: