Hi folks and first of all thanks for maintaining this crate!
We're using it to parse GitHub flavored markdown and stumbled on one of the spots where CommonMark and GFM disagree. CommonMark example 96 explicitly renders Foo\n- as <h2>Foo</h2>, but GFM §4.3 Setext headings says (emphasis mine):
A setext heading underline is a sequence of = characters or a sequence of - characters, with no more than 3 spaces indentation and any number of trailing spaces. If a line containing a single - can be interpreted as an empty list item, it should be interpreted this way and not as a setext heading underline.
Unsurprisingly, this crate is CommonMark compliant. However, I was wondering if you'd be willing to support GFM behaviour gated by Options::ENABLE_GFM.
If you're generally positive towards this change, I'd be happy to take a stab at a PR.
Hi folks and first of all thanks for maintaining this crate!
We're using it to parse GitHub flavored markdown and stumbled on one of the spots where CommonMark and GFM disagree. CommonMark example 96 explicitly renders Foo\n- as
<h2>Foo</h2>, but GFM §4.3 Setext headings says (emphasis mine):Unsurprisingly, this crate is CommonMark compliant. However, I was wondering if you'd be willing to support GFM behaviour gated by
Options::ENABLE_GFM.If you're generally positive towards this change, I'd be happy to take a stab at a PR.