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
This means that comments containing fenced code blocks -- which are rendered server-side as <pre><code>some code here\nanother new line</code></pre> -- have their \n newline characters ignored when the client-side JS renders, and so the whole output gets rendered on one line. This makes code blocks hard to read.
I'd quite like to keep these newline characters when the comment is rendered. I tried just commenting that newline-stripping line of code, and everything seems to work. Is there a reason for this line being there?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello isso'ers!
I noticed that the client-side JS strips newlines from the output in
isso/js/app/template.js
.https://github.com/posativ/isso/blob/178912d4426155201a67e0a95cff0ac201494d28/isso/js/app/template.js#L67-L68
This means that comments containing fenced code blocks -- which are rendered server-side as
<pre><code>some code here\nanother new line</code></pre>
-- have their\n
newline characters ignored when the client-side JS renders, and so the whole output gets rendered on one line. This makes code blocks hard to read.I'd quite like to keep these newline characters when the comment is rendered. I tried just commenting that newline-stripping line of code, and everything seems to work. Is there a reason for this line being there?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions