Skip to content

fix: preserve encoded brackets in relative file links - #259

Merged
vycdev merged 1 commit into
vycdev:developfrom
vycdev2:fix/encoded-file-link-delimiters
Oct 24, 2026
Merged

vycdev merged 1 commit into
vycdev:developfrom
vycdev2:fix/encoded-file-link-delimiters

Conversation

@vycdev2

@vycdev2 vycdev2 commented Oct 24, 2026

Copy link
Copy Markdown

Summary

  • Keep URL-encoded opening delimiters paired with literal closing delimiters in relative file links, and exclude unmatched literal closers when their match is encoded.
  • Add regression tests for link ranges and resolved filenames; update the unreleased changelog.

Verification

  • ./node_modules/.bin/mocha -r ts-node/register test/file-links.spec.ts --grep 'Relative file links' --exit — red on develop (2 regression cases failed before the fix).
  • npm test — passed (439 tests).
  • npm run compile — passed.
  • npm run format:check — passed.
  • npm run typecheck — passed.
  • git diff --check — passed.

Risk

  • Low: changes only trailing-punctuation handling for explicit relative file:// links; ordinary links retain their existing behavior.

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

@vycdev
vycdev merged commit 55dadfb into vycdev:develop Oct 24, 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