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.
Add a heading extraction example to the README and matching usage guide, as requested in #298. It shows heading levels, raw title wikitext, and plain text titles. The explanation distinguishes top-level filtering from nested nodes and points to
get_sections()for section content.Fixes #298.
Validation: executed both documentation snippets with the C and Python tokenizers (20 doctest checks), plus nested-heading and empty-selection checks. Full pytest: 2006 passed, 1 skipped. Strict Sphinx builds report the same 216 warnings on the unchanged base and this change, with no new warning messages. Other platforms and Python versions were not tested locally.
Developed and validated with OpenAI Codex.