fix(editor): batch initial collaboration projections atomically - #587
Draft
marcodantonio-netsons wants to merge 1 commit into
Draft
marcodantonio-netsons wants to merge 1 commit into
marcodantonio-netsons wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Initial collaboration sync previously committed each projected row separately, repeatedly notifying editor subscribers and pruning selection. Collect initial socket tasks over a 16 ms frame and commit the rows and shell together. Keep write gates closed until the server seed has reached the store, while retaining microtask projection for live peer edits and synchronous undo/redo. Extract document projection from the binding into its own module.
Regression coverage verifies a 30-page burst causes one site update, rejects a premature write, exposes all server titles when the write waiter resolves, and still projects live edits in the next microtask. Verified with bun test (7,054 passed), bun run build, bun run lint and git diff --check. Full large-site browser responsiveness remains under investigation. No database changes.