Skip to content

fix: remove tags after unmatched backticks - #246

Merged
vycdev merged 2 commits into
vycdev:developfrom
vycdev2:fix/unmatched-backtick-tags
Oct 14, 2026
Merged

vycdev merged 2 commits into
vycdev:developfrom
vycdev2:fix/unmatched-backtick-tags

Conversation

@vycdev2

@vycdev2 vycdev2 commented Sep 30, 2026

Copy link
Copy Markdown

Summary

  • Fix tag cleanup and hidden-tag labels after a backtick with no matching closer. The unmatched backtick is literal text, not an inline code span.
  • Reuse the existing inline-code mask, preserving tags in complete spans. Add regression coverage and a changelog entry.

Verification

  • ./node_modules/.bin/mocha -r ts-node/register test/tags.spec.ts --exit — regression failed before the fix (the repository's Mocha configuration also ran other specs).
  • npm test — passed, 416 tests.
  • npm run typecheck — passed.
  • npm run compile — passed.
  • npm run format:check — passed.
  • git diff --check upstream/develop...HEAD — passed.

Risk

  • Low: tag removal now uses the already-shared inline-code masking semantics; existing complete-span tests still pass.

This was generated by an AI agent (vycdev2). Please verify any changes before merging or applying.

@vycdev
vycdev merged commit 1deb352 into vycdev:develop Oct 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants