Derive semantic Markdown changes - #9047
Draft
hweihwang wants to merge 1 commit into
Draft
Conversation
Parse immutable documents, normalize their semantic structure, and emit bounded stable change descriptors. Support one shared schema for both parsed documents. Assisted-by: Codex:gpt-5.6-sol Signed-off-by: Hoang Pham <hoangmaths96@gmail.com>
This was referenced Aug 14, 2026
Author
|
Note on CI: the |
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.
Version comparison for Collectives pages has been requested in #599 for a long time. The core gap lives in Text: nothing could tell you what actually changed between two Markdown revisions. A byte diff says edits happened. It does not say that a paragraph was inserted, a link target changed, or a table row moved.
This PR adds the model that answers that: two Markdown documents in, a typed list of changes out. It is the foundation only, so there is no UI yet and no screenshot. The next three PRs build the views on top of it.
What's in this PR
Design notes
Stack
First of six, followed by #9048, #9049 and #9050 in this repo (each based on the one before), then nextcloud/collectives#2699 and #2700.
Verification
ts:checkandlintpass. The complete suite passes at this tip: 1,768/1,768, re-run on 2026-08-14. I also re-checkedSyncService.spec.tsin isolation at a clean checkout of basefd0155f6be: it passes there too. Zero drift against upstreammain, cleanmerge-tree, cleandiff --check, clean worktree, backup refs match.Related
Happy to answer any questions in review.