You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a workaround, I've hacked the renderer.js to ignore blocks where the content is numeric or has quotes. A longer term solution might be to ignore links that are in code blocks, but I don't know what would work for everyone.
The text was updated successfully, but these errors were encountered:
yeah, apparently the markdown renderer that Jingo uses has some limitations. In another issue, someone suggested me to change the parser. I will take a look at it and I will see if this also fixes this problem.
Can you please attach here the hack you applied so I can see if I can generalised it?
To work around this, I added an ignore pattern to lib/renderer.js . The extractTags function had some avoidance patterns, so I included one that skipped brackets containing a number.
I did not consider making a pull request, because I don't think that this is universally useful; Labeling numeric footnotes, for instance, wouldn't be possible as it is after this change. For our current use-case, though, it's satisfactory.
We have a fair bit of code examples in our jingo wiki, and we've noticed that condensed code can be rendered as links.
this comes out as
As a workaround, I've hacked the renderer.js to ignore blocks where the content is numeric or has quotes. A longer term solution might be to ignore links that are in code blocks, but I don't know what would work for everyone.
The text was updated successfully, but these errors were encountered: