Aidan Woods

I think this behaviour would be a good fit for inclusion in the GFM spec as it is very analogous to the spec's way of omitting a table body, and...

> Since Parsedown is a rather small and manageable project we shouldn't introduce a complex plugin system, Hooking and passing certain variables by reference to plugins using a `ParsedownPluginInterface::handleEvent(string $eventName,...

> adding more and more complexity just to maintain a very fragile compatibiliy to old extensions. Just for visibility, these are the compatibility layers I'm talking about (they're effectively equivalent...

Right then, let's go for 2.0. https://github.com/erusev/parsedown/tree/2.0.x

In CommonMark, links with spaces are supported by either writing the URL encoded characters (i.e. `%20`), or by enclosing the link in angle brackets (e.g. `[phonelink]()`). Parsedown doesn't currently support...

Having a quick look at the PHP library, it indicates: > If you are using PHP SmartyPants with another text filter function that generates HTML such as Markdown, you should...

Thanks for reporting, I'll fix this for the upcoming release :)

Is is a generic issue in CommonMark too, which [suggests](https://spec.commonmark.org/0.29/#example-278) separating lists with an invisible block (blank HTML comment): > To separate consecutive lists of the same type, or to...

There's a PR open for this (https://github.com/erusev/parsedown/pull/580). GitHub flavoured markdown actually already has a concept of bodyless tables (i.e. neither body rows, nor `` is generated). If possible it would...

Does `->setBreaksEnabled(true)` give the functionality you're after (it's not exactly `\n` -> `` but it aims to replicate GitHub's behaviour).