CommonMark support

[philsturgeon]

Hey, how CommonMark is this?

Markdown parsers all seem to build their own unique flavor of Markdown each and every time, usually because they copy and paste around test suites from random other projects then miss updates and changes without noticing.

Sorry for the self link, but I wrote about the mess a bit here.

CommonMark would be awesome, especially if you work from their spec.

[a8m]

@philsturgeon, thanks for this great post, very professional and informative. For your question, seems like I covered most of the things of CommonMark, but my first goal was to implement GFM for v0.1.0 (so, I think there's some conflicts between the specs). In version v0.2.0, I'm gonna make the rendering configurable based on specific spec (and CommonMark will be one of them).

Thanks.

[philsturgeon]

I gotcha. GFM and CommonMark are pretty close, so they don’t conflict. GFM is mostly a superset.

We made a CommonMark parser for PHP, which allows for customization:

http://commonmark.thephpleague.com/customization/overview/

Copying this approach, you can add a GFM extension, which supports tables and all that cool shit not in CM itself. :)

[a8m]

Oh, my mistake, you're right! I had to look at the GFM spec more deeply. thanks for this resource. time to work :)

[skyzyx]

:+1: