Skip to content

fix(markdown): persist browser editor changes - #2971

Draft
George Ng (GeorgeNgMsft) wants to merge 1 commit into
georgengmsft-markdown-browser-serverfrom
georgengmsft-markdown-browser-persistence
Draft

fix(markdown): persist browser editor changes#2971
George Ng (GeorgeNgMsft) wants to merge 1 commit into
georgengmsft-markdown-browser-serverfrom
georgengmsft-markdown-browser-persistence

Conversation

@GeorgeNgMsft

Copy link
Copy Markdown
Contributor

Summary

Final layer of the replacement stack for #2940, based on #2969 (georgengmsft-markdown-browser-server).

  • persist browser autosave and explicit saves with binding tokens and expected revisions
  • preserve serialized Markdown syntax and surface serializer failures
  • reject stale or incomplete binding/snapshot/switch data and reconcile only identical-content conflicts
  • preserve same-file bindings, nested document paths, and opaque collaboration room IDs
  • assign and transfer the primary browser autosave role while retaining headless compatibility

Validation

  • markdown package build
  • focused browser persistence and view-service suites: 17 tests passed
  • full markdown suite: 8 suites, 64 tests passed
  • package Prettier check
  • lint, complexity, circular-dependency, and test-debt ratchets
  • git diff --cached --check

The layer changes 1,377 lines, below the 1,500-line cap.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant