Add gh_ids: derive heading ids by GitHub's rules - #54
Merged
Conversation
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.
Rewritten from @PiotrCzapla's #43, keeping his corpus-validated slug rule (2285/2290 anchors across 196 GitHub wiki pages) and his tests. Closes #43.
gh_ids=Trueonmdhtml2htmlandmd2htmlderives automatic heading ids by GitHub's rules instead of the dialect's, so anchors match a GitHub-rendered page and links written against one keep working. Off by default.Two changes from #43: a bool instead of a
slug=mode string, and a heading whose slug comes out empty mints no id (id=""is invalid HTML and unaddressable, on GitHub too) while still holding its dedupe slot, so repeats take -1, -2 in step with GitHub. Details are in DIALECT.md's automatic heading ids paragraphs.