Skip to content

fix(markdown): preserve Windows file links - #1470

Merged
vastsa merged 1 commit into
mainfrom
fix/windows-markdown-file-links
Oct 8, 2026
Merged

vastsa merged 1 commit into
mainfrom
fix/windows-markdown-file-links

Conversation

@vastsa

@vastsa vastsa commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • Encode legal Windows drive-path destinations in existing inline and reference-style Markdown links before the default sanitizer filters them.
  • Route decoded clicks through the existing file opener, preserving the current main-process access checks and URL sanitization.
  • Add rendered Markdown regression coverage and update the file-reference E2E scenario.

Validation

  • Regression test failed on the previous code with <a>test.js</a> and passed after the fix.
  • Targeted chat-link/rendering and file-resolution suites: 104 tests passed.
  • pnpm build:js passed.
  • Desktop typecheck, desktop lint, and pnpm check:pr-base passed.
  • verify:ui:* was not run, per task instruction; the running desktop instance was not used.

Markdown destinations with drive letters were filtered as URI schemes
before the existing file opener could handle them. Normalize parsed
absolute Windows paths during the Markdown pass and decode them through
the current click path, keeping sanitization and file access checks intact.
Copilot AI balanced review requested due to automatic review settings October 8, 2026 03:45

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@vastsa
vastsa merged commit 27da36b into main Oct 8, 2026
5 checks passed
@vastsa
vastsa deleted the fix/windows-markdown-file-links branch October 8, 2026 03:50
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