Markdown: code in callouts, link labels and double-backtick spans renders with its backticks showing

Aperta
  • Qualcosa non va?
#2,718 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@uvw ci sta già lavorando.

Dal 5/11/2026.

  • #2719 di @uvw — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
frontend, web-dev

Direzione di ricerca

The report says annotate and Inbox use InlineMarkdown and a block parser; start by locating those entry points and reproducing with the Markdown sample in the issue. Compare parsing of double-backtick spans, link labels, and fences inside callouts with plain blockquotes. The issue says a fix is in PR #2719, so review that change and verify each expected rendering before taking further work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happened?

Code inside some other Markdown constructs renders with its backticks showing instead of as code. Seen in annotate and in Inbox messages; plan review and code review render through the same InlineMarkdown and block parser:

  • A code span holding a backtick. `` git log --format=`%h` `` shows its backtick runs: only single-backtick spans are recognized.
  • Code in a link's label. [`README.md`](…) and [the `card --help` page](…) show the backticks inside the link: a link's label is drawn as raw text.
  • A fence inside a GitHub callout. A fenced block inside > [!NOTE] (directly, or under a list item) renders as one line of inline code with stray backticks. The same fence in a plain > quote renders correctly.

To reproduce, annotate this file (plannotator annotate code-in-blocks.md):

# Code inside other Markdown

## Code span holding a backtick

Run `` git log --format=`%h` `` to list short hashes.

## Code in a link's label

- See [`README.md`](https://example.com/readme) for setup.
- Open [the `card --help` page](https://example.com/help).

## Fence inside a callout

> [!NOTE]
> Run this first:
>
> ```bash
> plannotator update --check
> ```

## Fence under a list item, inside a callout

> [!TIP]
> - Install the tools:
>
>   ```bash
>   bun install
>   ```

## Fence inside a plain quote (already works)

> Run this first:
>
> ```bash
> plannotator update --check
> ```

Expected: each construct renders as GitHub renders it: the code span with its inner backtick, code inside the link, and the fence as a code block inside the callout.

Annotate view of the sample: stray backticks around the code span and inside both link labels, and each callout fence shown as one line of inline code

A fix is in #2719. Fenced blocks opened with ~~~ are not recognized either; that is a separate change, so it is not part of this report.

Plannotator version

plannotator 0.28.50

OS

macOS

Agent

Claude Code

Where did it happen?

Annotate, Inbox

Browser

Chrome 156

Lingua principale
TypeScript
Stelle
8.7k
Fork
649
Merge medio
8h 40m
PR unite (30g)
786

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di backnotprop/plannotator

Tutte le issue di backnotprop/plannotator

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.