fix(editor): avoid shell reconstruction for existing row syncs - #585
Draft
marcodantonio-netsons wants to merge 2 commits into
Draft
marcodantonio-netsons wants to merge 2 commits into
marcodantonio-netsons wants to merge 2 commits 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
1 participant
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.
Each initial collaborative row sync previously reprojected and revalidated the whole site shell, even for pages/components already loaded over HTTP. On large sites this repeats shell work once per row. Reassemble rosters only when a newly discovered peer row arrives; existing rows retain their independent projection.
Regression tests verify stable shell identity across existing page syncs and correct roster order for new peer pages. Verified with bun test (7,055 passed), bun run build, bun run lint and git diff --check. No database changes. Full large-site editor responsiveness remains under investigation.