Sometimes what is provided by common markdown is just not enough and i use embedded HTML. And i just noticed that links with path parameters are not parsed correctly. For example, in the demo app
<a href="http://example.com/page?foo=bar">link</a>
<a href='http://example.com/page?foo=bar'>link</a>
[link](http://example.com/page?foo=bar)
will all give different results. I am not sure if this is a problem of the library or the dependency, but it seems like someone gives = sign more priority than the quotes, so it starts parsing next HTML attribute instead of completing a link. The funny part is that double quotes consumes one additional from the parameter name, e.g. foo=bar becomes fo. I'd like to know if there is a workaround. Great library btw.
Sometimes what is provided by common markdown is just not enough and i use embedded HTML. And i just noticed that links with path parameters are not parsed correctly. For example, in the demo app
will all give different results. I am not sure if this is a problem of the library or the dependency, but it seems like someone gives
=sign more priority than the quotes, so it starts parsing next HTML attribute instead of completing a link. The funny part is that double quotes consumes one additional from the parameter name, e.g.foo=barbecomesfo. I'd like to know if there is a workaround. Great library btw.