Markdown parser on’s extension page breaks fenced code blocks

Not an API bug report per se, but I wanted to signal the Markdown parser generating the extension description pages on does not handle fenced code blocks. For instance, this is how my extension’s install instructions from the REDAME look on

The original Markdown, in case you cannot guess, is:

brew install eslint


npm install -g eslint

# or

yarn install eslint

which both Github and Discourse handle just fine, BTW.

Thank you Martin!

I’ll forward this along to our web team.

1 Like