Repository navigation
inlineCode inside table been parsed incorrectly #80
Description
Initial checklist
- I read the support docs
- I read the contributing guide
- I agree to follow the code of conduct
- I searched issues and discussions and couldn’t find anything (or linked relevant results below)
Affected package
remark-gfm@4.0.1
Steps to reproduce
import remarkGfm from "remark-gfm";
import remarkParse from "remark-parse";
import { unified } from "unified";
const processor = unified().use(remarkParse).use(remarkGfm);
const text = `
| a |
| ------- |
| \`b \\| c\` |
`;
const file = await processor.run(processor.parse(text));
console.log(file.children[0].children[1].children[0].children[0]);Actual behavior
{
type: 'inlineCode',
value: 'b | c',
position: {
start: { line: 4, column: 3, offset: 27 },
end: { line: 4, column: 11, offset: 35 }
}
}
Expected behavior
The value should be b \| c.
Runtime
node@22.14.0
Package manager
yarn
Operating system
Windows
Build and bundle tools
No response
Activity
seiyab commentedon Dec 9, 2025
I suspect that it's correct in remark-gfm side.
|in inline code have to be escaped if it's in table cell.https://github.github.com/gfm/#example-200
↓ Rendered as
b | cSo Prettier needs its own workaround, I suppose.
fisker commentedon Dec 9, 2025
I didn't know it renders as
b | c. Thanks!github-actions commentedon Dec 9, 2025
wooorm commentedon Dec 9, 2025
yep, this is how it works in GFM tables!