Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Relative file links with non-ASCII paths don't open

Open Beginner friendly
#16,096 3 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@JDeffner is already working on this.

Since Oct 5, 2026.

  • #16071 by @JDeffner — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in packages/client-runtime/src/markdownLinks.ts and inspect parseMarkdownFileLink, then reproduce the issue with a bare relative path containing non-ASCII characters. Done when clicking that link opens the local file without requiring a ./ prefix; check for relevant existing tests in the client runtime.

Written by the indexing model from the issue text.

Description

bug via-triage

I was studying for a midterm while abroad and asked chat for a past exam. It linked a real file:

Summer 2026/.../pastexam/線性代數/2025_midterm_exam1_易志偉_1222.pdf

Clicking it didn't open the PDF.

Steps

  1. In chat, use a bare relative link whose path contains non-ASCII characters, with no ./ prefix.
  2. Click it.

Expected
The local file opens.

Actual
parseMarkdownFileLink only accepts bare relative paths matching [A-Za-z0-9._-] (packages/client-runtime/src/markdownLinks.ts on main @ 1604ccc). The Chinese characters fail that check, so the link is treated as a web link. Percent-encoding doesn't help, because the path is decoded before the check.

Workaround
Prefix the path with ./.

macOS, T3 Code.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
8h 34m
Merged PRs (30d)
243

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.