Repository navigation
fix: parse links generated by inline tokenizers - #4204
Merged
UziTech merged 1 commit intoNov 16, 2026
Merged
Conversation
|
@jaredrainsha is attempting to deploy a commit to the MarkedJS Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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
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.
Marked version:
7bfa1f70e8756c6ee3e47c235a34556edbf48b49(18.1.3)Markdown flavor: n/a (extension API)
Description
An inline tokenizer can pass generated text to
this.lexer.inlineTokens(). If the original inline input has no), the nested tokenizer inherits the outer link fast-fail flag even when the generated text contains a link. For example:Each inline run now checks its own input once and restores the outer flag on return. The existing fast-fail for unterminated links remains in place. Marked demo for the generated Markdown shows the expected rendering; the extension itself cannot be represented in the demo URL.
Verification
npm teston Node 25.9.0 and Node 26.12.0: 1,989 spec tests and 249 unit tests passed, along with build, UMD/CJS, types, and lint. Tests ran from a path without spaces because the existing CLI tests construct unquoted shell commands.npm run build,npm run test:unit,npm run test:specs, andnpm run test:cjspassed.OpenAI Codex assisted with investigation, implementation, and validation.
Contributor
Committer