Skip to content

Conversation

@MaximBobylev
Copy link

@MaximBobylev MaximBobylev commented Dec 29, 2021

The problem described in the the issue could be simplified to parsing error in case of the following table

| header1 | header2 |
| --- | --- |
| ```a``` | ```b``` |

Instead of parsing values A and B into separate columns, these values are being concatinated into first column. PR adds one alternative into column value regex, which provides correct parsing of triple backtics

The problem described in the the issue could be simplified to parsing error in case of the following table
```
| header1 | header2 |
| --- | --- |
| \`\`\`a\`\`\` | \`\`\`b\`\`\` |
```
Instead of parsing values A and B into separate columns, these values are being concatinated into first column. PR adds one alternative into column value regex, which provides correct parsing of triple backtics
@k00ni
Copy link

k00ni commented Jan 28, 2022

Any update here? @erusev

@BenjaminHoegh
Copy link

@erusev This issue is also present in the current state of the 2.0 version of Parsedown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants