Repository navigation
test(parser): specify position-safe GFM autolink behavior - #155
Merged
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
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.
Background
The parser disables the GFM autolink-literal transform. That transform can create nodes without source positions.
Tokenizer-based autolinks remain enabled. The quoted
www.google.comcase needs a direct regression test and clear documentation.See remark-gfm issue #16.
Changes
www.example.comin the built package.www.google.comremains positioned text.parseMdandparseMdWithSourceMap.Compatibility
Runtime behavior does not change. The current GFM configuration remains in place.
Validation
pnpm testpassed: 2026 built tests and 11 source tests.pnpm run lintpassed.pnpm run test:coveragepassed. The report still maps tosrc/.git diff --checkpassed.No sensitive data was added or redacted.