xoofx / xoofx/markdig

Conditionally process url instead of encoding

Open
#667 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
C#
Stars
5.3k
Forks
510
Avg merge
8d 5h
Merged PRs (30d)
5

Description

Markdown links will automatically be URL encoded when turned into an HTML anchor.
Is it possible to process the url string instead of it gettingURL encoded?

For example:

This is [a test](#|MY_URL|#). Normal [link](https://url.com/my|title)

will be turned into:

This is <a href="#%7CMY_URL%7C#">a test</a>. Normal <a href="https://url.com/my%7Ctitle">link</a>

I want to match urls that start with #| and end with |# and replace that with *| and |* consecutively and skip url encoding (because it will be sent to another process that expects this format).
So that the output would be:

This is <a href="*|MY_URL|*">a test</a>. Normal <a href="https://url.com/my%7Ctitle">link</a>

Is that possible by creating an extension for example?

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 locating Markdig’s link-rendering path, URL-encoding logic, and available extension points. Verify completion against the issue’s examples: URLs wrapped in #| and |# become | and |, while ordinary URLs remain encoded.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, markdown
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.