Add support for cloning node trees - #3
Merged
Conversation
Assisted-By: devx/7ef83274-928f-499d-b668-48449b1ff60e
samuel-williams-shopify
force-pushed
the
add-node-cloning
branch
from
September 9, 2026 04:42
8f8b220 to
4b9fd22
Compare
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.
Summary
Add
cmark_node_cloneto create an independent structural copy of a node tree without serializing and reparsing Markdown. The clone preserves node metadata, source positions, inline code language information, and internal footnote relationships while deliberately excluding user data.Add an extension hook for copying opaque node state, with support for table metadata. Make HTML rendering safe for cloned standalone paragraph nodes, which no longer have a parent document.
Testing
make test