Repository navigation
Let the Markdown document supply inline content for each block - #109
Merged
trissim merged 2 commits intoOct 8, 2026
Merged
Conversation
trissim
marked this pull request as ready for review
October 8, 2026 00:29
trissim
changed the title
trissim
deleted the
refactor/native-markdown-token-content-owner-20261007
branch
October 11, 2026 20:05
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.
Markdown blocks converted their inline tokens to content themselves, leaving no place for a document to supply different content.
MarkdownBlock._token_to_contentin_markdown.pyis now static, andbuild_from_tokencalls a newMarkdown._get_token_content(token, block=...)hook. By default the hook runs the same block conversion, so ordinary documents behave as before. Two tests are added totest_markdown.py.