Join GitHub today
[discussion] markdown-js #3
I just started to add the testsuite to a markdown-js fork, but I don’t know yet if the author will be interested. Anyway, I think it could be useful for the markdown-testsuite.
markdown-js is supporting multiple dialects, I chose the default one, “Gruber”, which targets the Gruber documentation, like the specification.
Good news: markdown-js already passes 51 of the 102 tests ! Most of the failing tests I observed are related to spaces, line breaks, or attributes order.
I posted all the results here (
Do you think there are things to fix in the suite, based on these results?
What do you think about integrating the testsuite into the popular markdown parsers? It could be a great way to push the Makdown Specification project while improving the interoperability among the existing tools, but maybe it’s too soon?
 Instructions to launch the testsuite with markdown-js:
hmmm. So that's the tricky part. When doing the test suite depending on how we output the html there will be layout differences. One way to deal with that would be to have a canonical representation. For example we could decide that
There must be others. I guess I can't really decide that. The implementers of the different libraries could decide. The important is that it is syntactically correct.
Some libraries are also generating things like automatic id for the headers. Should it be fixed or just ignored when testing.