Example tests:
The above all disappeared in the "Preview" pane and later in the actual rendering of this issue.
This is the markdown I used:
<path>
> <path>
*<path>*
**<path>**
> *<path>*
> **<path>**
As a workaround, use the backtick:
<path>
<path>
<path>
<path>
<path>
<path>
This is the backticked markdown:
`<path>`
> `<path>`
*`<path>`*
**`<path>`**
> *`<path>`*
> **`<path>`**
:wave: Please reach out to our support team with support requests in future — this repository is just for issues for the github-markup
gem, which doesn't relate to our Markdown parsing.
You'll want to escape the < and >; it's interpreted as an HTML tag and removed by our sanitizer.
\<path\>
Produces:
\
Thanks!
@kivikakk thanks for the workaround and the support team tip: I've filed a support request for this as a new feature referring to the current issue.
@jpluimers just as a heads up, I don't think there's any change likely to be made here. The current interpretation is per the GitHub Flavored Markdown spec, per CommonMark, and a change here would make us incompatible with CommonMark.
@kivikakk oh, I feel this #facepalm moment now: Markdown allows for in-line HTML, which had totally forgotten as I write most documentation in reStructuredText.
Thanks for reminding me!
@jpluimers aaaaaa, and I didn't realise it wasn't clear from your end that that was what was happening! We got there ❤️