Dom Christie

@jmurzy @hedgerwang Thanks for the clarification. I had seen https://github.com/facebook/react-native/commit/807726b, and was aware that some of the NavigationExperimental parts were going to be deprecated (e.g. containers), but I wasn’t entirely...

Well spotted! We'll probably need a fix for this, but in the meantime you may want to set the `emDelimiter` option to `*`, which I _think_ should fix it.

Thanks. This is a duplicate of #123

Just noticed that's a PR, so will reopen this issue.

Another possible solution would be to preserve `` elements when contained in an inline element. It seems valid: https://spec.commonmark.org/dingus/?text=_hello%3Cbr%3Eworld_

`language-` prefix is mentioned in the CommonMark spec: https://spec.commonmark.org/0.28/#fenced-code-blocks. However it does state: "this spec does not mandate any particular treatment of the info string", so we could make this...

Rather than digging into the internals, you may wish to try adding a custom rule to handle everything other than your subset. For example, something like: ```js turndownService.addRule({ filter: function...

Thanks for this! It’s an interesting case because I don’t think it’s possible to produce `Hello world` from Markdown, so it raises questions as to what the correct outcome is?!...

Thanks! I think the result of your most recent version is more inline with the outcome of the rendered HTML, however I am not entirely convinced that a converter is...

Perhaps ``` foobar ``` should convert to ``` _foo bar_ ``` which would then result in the following when converted back to HTML: ``` foo bar ``` This could be...