Skip to content

fix: make the no-proxy editor link clickable (https listing), drop install link#12

Merged
brovatten merged 1 commit into
mainfrom
fix/cta-clickable-editor-link
Jun 6, 2026
Merged

fix: make the no-proxy editor link clickable (https listing), drop install link#12
brovatten merged 1 commit into
mainfrom
fix/cta-clickable-editor-link

Conversation

@brovatten
Copy link
Copy Markdown
Member

The no-proxy editor link used a vscode:/cursor: deep link, but GitHub's comment sanitizer strips custom URI schemes — confirmed on PR #365's rendered HTML, where Open in VS Code → came back as <strong>, not <a>. Only http(s)/mailto survive.

Fix: point the no-proxy editor link at the extension's https listing (Marketplace for VS Code, Open VSX for Cursor) — clickable on GitHub — and drop the redundant Get the extension line. The proxy path (cta_base_url set) is unchanged; it already uses https and deep-links via redirect.

44 tests pass.

…link

GitHub's comment sanitizer strips custom vscode:/cursor: URI schemes, so the
editor deep link rendered as dead bold text, not a link. Point the no-proxy editor
link at the extension's https listing (VS Code Marketplace, Cursor via Open VSX),
which GitHub keeps clickable, and drop the now-redundant 'Get the extension' line.
The proxy path (cta_base_url set) is unchanged — it already uses https and can
deep-link via redirect.
@brovatten brovatten merged commit eed6a26 into main Jun 6, 2026
2 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.

1 participant