GFM URL Linking: Configuration Option to Suppress Links Inside Code Spans and Blocks

Answer

The configuration flag should be named urlLinkInCode (boolean). Its default must be true to preserve existing GFM behavior where URLs inside backticks or fenced code blocks are automatically turned into links.

How to expose the option

• Parser API – add the field to the options object, e.g. MarkdownIt({ urlLinkInCode: false }) or md.set({ urlLinkInCode: false }) for MarkdownIt‑based GFM parsers; other libraries should mirror this boolean in their config struct.
• CLI – provide a toggle such as --no-url-link-in-code (or --url-link-in-code=false) that sets the option to false; the default invocation leaves it true.

Expected latency impact

When many URLs appear inside code spans or blocks, disabling the linkify step avoids the regex scanning and attribute generation for those URLs. In practice this can reduce per‑document CPU time, but the exact gain depends on the proportion of URLs inside code and the workload concurrency. A benchmark is required to quantify the improvement (e.g., 10‑30 % under high concurrency for documents where a large fraction of URLs are inside code).

Verification needed

To confirm the benefit, create a markdown file (≥100 KB) with thousands of URLs inside inline backticks and fenced blocks plus an equal number of regular‑text URLs, run the parser concurrently (e.g., 50 workers) with the flag true and false, measure average latency and throughput with a load‑testing tool such as wrk or ab, and verify that regular‑text URLs still produce <a> tags while URLs inside code do not when the flag is false.