CommonMark support

[ericpoulinnz]

Is CommonMark support actually coming? I noticed in the README it says it is, but then I saw that line was added in January of last year... are there any updates?

Most of my issues with this library has been in customising the parsing logic to handle the differences between ExpeniMark and CommonMark. It would have never been a problem if MarkdownText was implemented (so I could have used ExpeniMark on both view/edit modes), but I had to go with a different Markdown view renderer which supports the much more standard CommonMark.

[tomekzaw]

@ericpoulinnz Not really, we don't support CommonMark out-of-the-box – however, you can pass your own Markdown parser as a worklet to parser prop of MarkdownTextInput component to fully customize parser logic.

[ericpoulinnz]

@tomekzaw I feel then you should update this section, because that's a bit misleading if it's not actually planned.

Yes I implemented a custom parser, thanks. However this issue is about CommonMark support in this library as stated was coming in the README. So if that's not the case, I think updating that makes most sense.

[tomekzaw]

@ericpoulinnz I've removed the part about CommonMark parser in #727, thanks for suggesting that.