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
There is a bug where specific words in a code block set to use line numbering will cause some empty following lines to have spurious {1} text inserted in it. e.g.:
this can be confirmed by inspecting the <code class> element it will be set to hljs sql for blocks with this issue and hljs perl or other wise for blocks of code without this issue.
This only happens if the code language is autodetected as SQL (hence why the specific words are needed to trigger the highlight.js autodetection for SQL). if the language type is set to SQL or any other type it does not happen:
If line numbering for SQL is turned off in the markdown plugin settings it does not happen:
(note no line numbering, no {1})
So we can work around this issue by just not having line numbering for SQL as we don't post SQL frequently/at all on our forum.
Versions:
NodeBB version: 1.18.5 (although we have had this issue from at least 1.16)
Markdown plugin version: 8.14.4
The text was updated successfully, but these errors were encountered:
There is a bug where specific words in a code block set to use line numbering will cause some empty following lines to have spurious
{1}
text inserted in it. e.g.:this can be confirmed by inspecting the
<code class>
element it will be set tohljs sql
for blocks with this issue andhljs perl
or other wise for blocks of code without this issue.This only happens if the code language is autodetected as SQL (hence why the specific words are needed to trigger the highlight.js autodetection for SQL). if the language type is set to SQL or any other type it does not happen:
If line numbering for SQL is turned off in the markdown plugin settings it does not happen:
(note no line numbering, no
{1}
)So we can work around this issue by just not having line numbering for SQL as we don't post SQL frequently/at all on our forum.
Versions:
NodeBB version: 1.18.5 (although we have had this issue from at least 1.16)
Markdown plugin version: 8.14.4
The text was updated successfully, but these errors were encountered: