Error parsing < and > about markdown-to-jsx

[quantizor]

Yuck, looking into this. Thanks for reporting.

[quantizor]

Fix is out in 6.6.6 thanks! https://github.com/probablyup/markdown-to-jsx/releases/tag/6.6.6

[niallel]

Thanks so much, it fixes the first issue but it doesn't fix the second issue.

When there is
<Markdown>{'1<a or 2>1'}</Markdown>
It will be output as
11

Any ideas?

[quantizor]

That one is more difficult to solve; will have to think more on it.

The problem is it is being detected as an <a> tag and then probably thrown out on render since the syntax is invalid, resulting in 11. We don't validate individual attribute groups at HTML detection time or do any enforcement of self-closing vs normal html syntax to save on library size (would introduce a fair amount of code.)

[niallel]

Maybe allow
> <
to be displayed correctly.

At the moment if you pass <Markdown>{'&gt;'}</Markdown> then > will be shown.

If you parsed those and displayed as > < then you wouldn't need to worry about this.

[quantizor]

Yes but one of the important parts of this library is supporting the html syntax. So if I did that, the html wouldn’t work. This is just an edge case to be overcome

[niallel]

Thanks, I completely understand your reasoning.

Maybe its my understanding, but > gets displayed correctly by the browser as >
But when its inside the browser doesn't render it correctly.

I've worked around it by putting spaces around < or > as there shouldn't be any HTML in my input, just curious as to why when I pass in > it doesn't get shown correctly.