Error in documentation / bug in Markdown

[aleroma]

Here wrong example for <exclude> alias - {<em> text-block </em>}. It seems that correct example should be - {*<em> text-block </em>*}.

[Rayne]

Thanks for the report. Please use the documentation's issue tracker (F3Community/F3com-data/issues) for future findings.

---

That's a tricky Markdown parser problem. I am not sure if it's possible to create inline <code> tags with the current parser without evaluating the tag's content (e.g. *italics*). Replacing

`{* text-block *}`

with

```{* text-block *}```

or

<code>* text-block *</code>

doesn't fix the problem and

\```
{* text-block *}
\```

(without the \) isn't a valid solution as it breaks the listing.

---

(GitHub doesn't interpret code tag values and parses it as expected.)

[xfra35]

Looks like a bug in the markdown library as the original spec states:

Regular Markdown syntax is not processed within code blocks. E.g., asterisks are just literal asterisks within a code block.

For now, I've encoded asterisks: https://github.com/F3Community/F3com-data/commit/6e92f0fa21151c01406816547e8eeeebccf18b83

[aleroma]

Well done! Thanks for quick fixing. Who can close the issue?

[xfra35]

Well before closing it, the question is: do we fix the Markdown class or not?

[Rayne]

I didn't expect this behaviour, so :+1: for fixing instead of working around with encoded characters.

[bcosca]

No objections here