No charts found when space between opening code fence and language name about mermaid-cli HOT 3 OPEN

I suppose this line about not rolling your own markdown parser proved to be prophetic 😉

😆

The main reason we haven't switched yet is that:

• There are many implementations of Markdown, and we don't want to just support GFM when people might be using Pandoc markdown (or some other arbitrary Markdown spec)
• We didn't want to make breaking changes for existing users.

However, we're planning on making a v11 release once Mermaid makes a v11 release, and we're planning on finally dropping support for Node.JS v14 & Node.JS v16. So dropping support for some more unusual Markdown implementations might be okay too.

As a temporary measure, here are two remark plugins that actually use a real markdown parser that you can use:

• remark-mermaid-dataurl: Uses mermaid-cli under the hood, and embeds the generated SVGs into the markdown file as data URLs.
• remark-mermaidjs: Embeds the generated SVGs in the markdown as plain SVGs.

from mermaid-cli.

Sounds like a plan! My toolchain involves pandoc for manipulating and combining markdown files before running mermaid-cli, so for future Googlers in the same situation for now, my solution was to write a very crude Lua filter to 'process' the mermaid code blocks explicitly:

function CodeBlock(elem)
    local language = pandoc.utils.stringify(elem.classes)
    if FORMAT:match 'gfm' and language == 'mermaid' then -- don't forget to change the markdown format here or make this more generic if needed
        return {
            pandoc.RawInline('markdown', '```mermaid'), -- basically just hardcode the block without the space
            pandoc.RawBlock('markdown', elem.text),
            pandoc.RawInline('markdown', '```')
        }
    end
    return elem
end

from mermaid-cli.

I suppose this line about not rolling your own markdown parser proved to be prophetic 😉

from mermaid-cli.