-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipes |
not rendering correctly in cells with Marked renderer
#138
Comments
Adding the following to my
In both case the render is <p><code>||</code></p>
<table>
<thead>
<tr>
<th>a</th>
<th>b</th>
</tr>
</thead>
<tbody>
<tr>
<td>`</td>
<td></td>
<td>`</td>
<td><code>pipe pipe</code></td>
</tr>
</tbody>
</table> |
Have you tried the Raw tag? `||`
a | b
--- | ---
`<%raw%>||<%endraw%>` | `pipe pipe` |
This is an issue with Marked itself - not Hexo. See issue here in Marked repo. Interim fix is to use html which will render as desired in Hexo (but does not render properly in GFM).
|
@dpfranklin : Thanks, I was not sure if it was due to Marked or only hexo-renderer-marked. |
Marked seems no so much updated recently (markedjs/marked#724). And Marked is not CommonMark compliant (markedjs/marked#563). It's maybe time to switch (as official) to commonmark.js, markdown-it or remarkable. There are already markdown-it, kramdown and pandoc hexo-render alternatives. |
I tried hexo-renderer-markdown-it and the both cases works well now (with default which is GMF support) :
|
|
not rendering correctly in cells with Marked renderer
Maybe Hexo team should think about considering to use markdown-it renderer as default and official renderer, because Marked seems to begin to die (markedjs/marked#724). |
markedjs/marked#595 closed. |
Environment Info
Node version(
node -v
)Plugin version(
npm ls --depth 0
)BUG
Description : pipes inside inline code block inside an array don't display correctly.
Markdown code:
Bugous behaviour:
Espected behaviour:
I may also open this bug into marked and hexo-renderer-marked repositories. I also tried with a fresh hexo install and the behaviour is the same.
The text was updated successfully, but these errors were encountered: