VisActor / VisActor/VChart

[Documentation] Percent-encoded external hrefs render as broken relative links

Open
#4,658 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.8k
Forks
221
Avg merge
1d 6h
Merged PRs (30d)
26

Description

Documentation URL

Examples include:

Description

At develop commit 0750d74cd6ea734e66897876506c78ca12680676, 66 Markdown source files contain 190 link destinations whose entire URL is percent-encoded, for example:

[GitHub](https%3A%2F%2Fgithub.com%2FVisActor%2FVChart)

The deployed HTML preserves this as href="https%3A...". Browsers therefore treat it as a relative path under the current VChart page rather than an external URL. This is visible on the FAQ pages above, where clicking a reference navigates to a path such as /vchart/faq/https%3A....

The intended external URL should be emitted as a normal absolute href. A mechanical decode is not safe for the whole set: 21 of the encoded destinations point at an internal host, so those references need a public destination or an explicit decision to remove them before bulk correction.

I fetched all 4,627 open/closed issues and pull requests and searched their current titles and bodies for https%3A, percent-encoded links, and encoded URLs. The only unrelated match was #2462. The repository has no Discussions; the source history contains only the original documentation imports and no later fix. I found no current owner, linked PR, commit, or duplicate for this link-generation/content problem.

Contributor guide

Open the contributing guide

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.

Research direction

Start by inspecting the 66 Markdown source files containing the 190 percent-encoded destinations, using the FAQ URLs as visible examples. Separate external links from the 21 internal-host destinations before making bulk corrections; done means external URLs render as absolute hrefs and each internal reference has a public destination or an explicit decision to remove it.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.