Adopt bucket priorities in yjs demo #512
Open
+130
−887
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adopts bucket priorities in the yjs demo, where the effect of buckets with
priority: 0
is most obvious. In particular, this:global
buckets into one bucket for documents (with the default priority) and one for document updates (with priority 0).Running the demo with updated sync rules requires a self-hosted sync service for bucket priorities to be supported. The effect of priority 0 can easily be seen by:
Despite of the local crud queue in A, changes from B are synchronized and made visible :)