Aidan Woods

Thanks for reporting this! This one in particular is a known issue, and has the same root cause as your other issue: when parsing a list continuation, we should first...

See #707 for the more general issue. I'd originally closed this as a won't fix, but I have reconsidered and think that this can be implemented without introducing an unreasonable...

I'm not going to add this in 2.0, it can be done but requires a new parsing strategy (which is at odds with Parsedown's focus on speed/simplicity).

Thanks so much @nathanlesage. Even a review from the prospective of a user of the API would be helpful, sans a full on code review which I realise would be...

Hi @nathanlesage, Apologies for not getting to this sooner—time's been a bit scarce recently and I wanted to be able to give your review a proper run though. Thank you...

@erusev Any thoughts on the direction of the changes in this PR? I'd like to bring a branch of Parsedown-Extra in line with this codebase, get this ready for merge...

@BenjaminHoegh I've let this linger quite a while, haven't I... 😄 By all means feel free to work on an extension based on these changes. Any feedback you have would...

Just to track it here, if memory serves I think I had the following on my list of things to do before this could be released: - [x] Update Parsedown...

@BenjaminHoegh I've converted ParsedownExtra to be compatible with this branch over at https://github.com/erusev/parsedown-extra/pull/172. Currently, the plan would be for "extensions" in the new world to implement the `StateBearer` protocol (they...

There isn't. This is to make sure that mutations are localised and don't end up being in places where they weren't intended. As a plus to this approach, this means...