We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the Commonmark playground and the Commonmark spec, the string
"`\n`"
should be parsed into
[ Start(Paragraph) Code(" ") End(Paragraph) ]
since newline is normalized as a space.
However, when parsing the string with pulldown-cmark 0.9.3, I get
[ Start(Paragraph) Code("") End(Paragraph) ]
instead. I used this little test program:
use pulldown_cmark::{Event, Parser}; fn main() { let text = "`\n`"; eprintln!("{text:?} -> ["); for event in Parser::new(&text) { match event { Event::Code(code) => eprintln!(" Code({:?})", &*code), _ => eprintln!(" {event:?}"), } } eprintln!("]"); }
Note that "`foo\n`" and "`\nfoo`" are parsed correctly with a trailing and leading space, respectively.
"`foo\n`"
"`\nfoo`"
I found this while trying round-trip strings through pulldown-cmark-to-cmark (Byron/pulldown-cmark-to-cmark#55).
The text was updated successfully, but these errors were encountered:
"
I will check this for the next release, thanks for reporting it.
Sorry, something went wrong.
Thanks for taking a look!
"\n "
Check if fixed by #776.
No branches or pull requests
According to the Commonmark playground and the Commonmark spec, the string
"`\n`"
should be parsed into
since newline is normalized as a space.
However, when parsing the string with pulldown-cmark 0.9.3, I get
instead. I used this little test program:
Note that
"`foo\n`"
and"`\nfoo`"
are parsed correctly with a trailing and leading space, respectively.I found this while trying round-trip strings through pulldown-cmark-to-cmark (Byron/pulldown-cmark-to-cmark#55).
The text was updated successfully, but these errors were encountered: