Closed sylae closed 8 years ago
This appears to be an issue with the markdown processor we use. I don't see a config option documented to resolve this, so it'll probably end up with us moving to a different parser (probably whatever github uses, if it's not in some weird hipster language)
Ended up not using Github's parser, but the parser used now is, apparently, compatible with Github's flavor of markdown
Appears to be a potential issue with the Markdown processor. Hopefully there's a flag or something in the processor we can use, otherwise we might have to work with raw HTML until a better solution is found...