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

"~XXX~"are also parsed into erase lines #3636

Closed
M-1202 opened this issue Mar 7, 2025 · 2 comments
Closed

"~XXX~"are also parsed into erase lines #3636

M-1202 opened this issue Mar 7, 2025 · 2 comments

Comments

@M-1202
Copy link

M-1202 commented Mar 7, 2025

Marked version:
"marked": “^15.0.7”
Describe the bug
"XXX"are also parsed into erase lines.This is bug.Because only "XXX" should be parsed into erase lines

Image

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

@UziTech
Copy link
Member

UziTech commented Mar 7, 2025

If you look at your message both of them are parsed into erase lines on GitHub, so why do you think marked shouldn't parse one of them into erase lines?

@calculuschild
Copy link
Contributor

According to the Spec:

https://github.github.com/gfm/#strikethrough-extension-

Strikethrough text is any text wrapped in a matching pair of one or two tildes (~).

This seems like the correct behavior.

@UziTech UziTech closed this as completed Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants