-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
can't convert (\|) as (|) in table #595
Comments
@helphi Interestingly, I am also having trouble parsing tables with
This renders correctly on GitHub:
But it renders incorrectly on Gist and when using marked.js. |
The error in parsing might have something to do with robotskirt(the parser) failing to build. I got the error when I cloned the repo to get ready to debug locally. There is also failing test for me as well. If the parser is not working and it looks like its no longer being supported as well deprecation commit. Last commit to main repo is 11/2013. Currently looking into alternatives
|
I found out that roboskirt is no longer being supported. The recommendation is to use hoedown. I am looking into that now. |
I have a fix: Turns out the But the following will work for you
|
From https://github.com/hexojs/hexo/issues/2414 @bdougie is right, that doesn't work with backquote either. Description : pipes inside inline code block inside an array don't display correctly. Markdown code: `||`
a | b
--- | ---
`||` | `pipe pipe` 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 plan a permanent fix? |
@ZombineDev Problems comes from the parser : roboskirt. roboskirt is not more updated but node-hoedown seems not either. |
Also seeing it in this docsify issue |
This is allowed in GFM but not supported by marked. See this issue: markedjs/marked#595 Fixes #1187
…nt (#1204) This is allowed in GFM but not supported by marked. See this issue: markedjs/marked#595 Fixes #1187
for example:
The text was updated successfully, but these errors were encountered: