Skip to content
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

[Bug?] Possible incorrect parsing in markdig #783

Closed
nopeless opened this issue Mar 18, 2024 · 2 comments
Closed

[Bug?] Possible incorrect parsing in markdig #783

nopeless opened this issue Mar 18, 2024 · 2 comments

Comments

@nopeless
Copy link

Somehow I found the bug in Show-Markdown which lead me to Powershell/MarkdownRenderer which lead me to here

PowerShell/MarkdownRender#24

I am not a consumer of markdig, but by the way the renderer works I highly suspect that the incorrect renders are from this library

1. [links](#features)
2. `inline code`
3. normal text
4. line

- `also happens in ul`
- line

image

Output on my terminal

@nopeless
Copy link
Author

if it's not an issue from this library let me know. I don't know how to test it

@MihaZupan
Copy link
Collaborator

MihaZupan commented Mar 18, 2024

Markdig is working correctly here: https://babelmark.github.io/?text=1.+%5Blinks%5D(%23features)%0A2.+%60inline+code%60%0A3.+normal+text%0A4.+line%0A%0A-+%60also+happens+in+ul%60%0A-+line

This is likely a bug in Powershell/MarkdownRenderer, likely here https://github.com/PowerShell/MarkdownRender/blob/8be5371470e57c106c4eb5e6297115741dfcd8ba/src/ListBlockRenderer.cs#L36 (rendering the inline without the block itself)

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

No branches or pull requests

2 participants