VSCode Markdown Parser Bug for Extensions README.md

[ahmadawais]

I am about to launch a new theme next week, called Shades of Purple.

The issue is that the README.md file is being parsed completely fine at GitHub and at VSCode Marketplace. But inside VSCode the markup is not being parsed :(

Take a look at this screenshot.

• VSCode Version: 1.21.1

Environment:
  OS: macOS Sierra 10.12.6
  CPU: x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
  Node: 9.7.1
  Yarn: 1.5.1
  npm: 5.7.1
  Watchman: Not Found

Browsers:
  Chrome: 65.0.3325.181
  Chrome Canary: Not Found
  Firefox: 57.0.1
  Firefox Developer Edition: 57.0
  Firefox Nightly: Not Found
  Safari: 11.0
  Safari Technology Preview: Not Found

[mjbvz]

Bug in marked library. Opened markedjs/marked#1195 to track this upstream

[UziTech]

A quick fix would be to put new lines after the end of closing tags. demo

[ahmadawais]

Thanks @UziTech for the tip. I did that so the issue is resolved for now but Markedjs could really be improved by this.

[UziTech]

Thanks. We are currently trying to raise marked from the dead. Any help would be appreciated. 😁

[ahmadawais]

@UziTech I'll see what I can do apart from sharing it with my network 👍

[mjbvz]

Fixed by picking up a new copy of marked.

For verification, create an extension that has this README.md and preview it in the extension explorer: https://raw.githubusercontent.com/ahmadawais/shades-of-purple-vscode/2828bb0c51ba950790cf3e084475d125205a1921/README.md

Some headers and other content used to show up raw, i.e. as ### header in the output. This should not happen in fixed vscode versions