-
Notifications
You must be signed in to change notification settings - Fork 17
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
Doc awareness #277
Doc awareness #277
Conversation
@meeseeksdev please backport to 0.2.x |
Awww, sorry brichet you do not seem to be allowed to do that, please ask a repository maintainer. |
@meeseeksdev please backport to 0.2.x |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
jupyter_ydoc/ybasedoc.py
Outdated
@@ -31,6 +31,9 @@ def __init__(self, ydoc: Optional[Doc] = None): | |||
self._ydoc = Doc() | |||
else: | |||
self._ydoc = ydoc | |||
|
|||
self._awareness = awareness |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should just have:
self._awareness = awareness | |
self.awareness = awareness |
And remove the getter and setter as they do nothing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe we should only remove the setter, to make awareness
read only, it is not supposed to be set later.
What do you think ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the getter and setter.
Co-authored-by: David Brochart <[email protected]>
Co-authored-by: David Brochart <[email protected]>
It needs a release of pycrdt_websocket for the tests. |
I'll make one. |
Co-authored-by: David Brochart <[email protected]>
Do you mind reviewing jupyter-server/pycrdt-websocket#76 before? |
Co-authored-by: David Brochart <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @brichet, I guess you can remove the "draft" status?
Oh it's not in draft anymore, let's merge? |
I'll backport it manually |
* Add an awareness in the YDoc on server side * Test awareness getter/setter * Depend on pycrdt instead of pycrdt_websocket * Apply suggestions from code review Co-authored-by: David Brochart <[email protected]> * Apply suggestions from review Co-authored-by: David Brochart <[email protected]> * Apply suggestions from code review Co-authored-by: David Brochart <[email protected]> * Apply suggestions from code review Co-authored-by: David Brochart <[email protected]> * Update pycrdt_websocket for tests --------- Co-authored-by: David Brochart <[email protected]> Co-authored-by: David Brochart <[email protected]>
This PR add an optional awareness on the server side ydoc, to enable it to be aware of transcient state of clients.
Draft until jupyter-server/pycrdt#170 is merged and released.