Repository navigation
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.
Markdown indexing treats headings inside
~~~code blocks as real sections. A four-backtick example containing triple backticks also toggles the old boolean fence state early, adding code to the outline or hiding the following real heading.Track the opening marker and its length. Close only on the same marker, at least as long, with no trailing non-whitespace text. Support tilde fences and leave an unclosed fence active through EOF. This follows the fenced-block boundary rules in https://spec.commonmark.org/0.31.2/#fenced-code-blocks without adding a parser dependency.
Regression coverage includes tilde fences, nested shorter fences, mismatched markers, trailing text on an apparent closer, unclosed blocks, and preservation of the following heading's line number. The new cases reproduce the bug on main.
python -m pytest tests/test_page_index_md.py -qpasses, including both existing CLI tests.Related historical work: #246 and #249 addressed broader Markdown parsing problems and were closed on 2026-08-31 as superseded legacy implementations. This narrower patch targets the current
pageindex/page_index_md.pyfunction, which is still called bymd_to_treeandrun_pageindex.py. Rechecking current main on 2026-10-08 still produces a spuriouscodeheading for both tilde and nested-long-fence examples; this branch preserves onlyBeforeandAfter. No open PR implementing this specific fix was found in the refreshed search.Revalidation on 2026-10-08:
python -m pytest tests/test_page_index_md.py -qreports 5 passed and 4 subtests passed on local Python 3.14, including the CLI cases. This is not a claim that the upstream Python 3.10/3.13 CI matrix has passed. Earlier Actions runs report failure but expose no job logs identifying the cause.Reopened after revalidating the current code and related PRs. The previous author-side closure had no recorded explanation. AI-assisted contribution.