-
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
Fix lexer and tokenizer to retain line breaks properly #2341
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/markedjs/markedjs/8heK88jvf6Z7JZpS8ctiZnYCcij6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this! 💯
## [4.0.9](v4.0.8...v4.0.9) (2022-01-06) ### Bug Fixes * retain line breaks in tokens properly ([#2341](#2341)) ([a9696e2](a9696e2))
🎉 This PR is included in version 4.0.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Marked version:
4.0.8
Markdown flavor: n/a
Description
This PR stops ignoring single
\n
characters and makes sure they're properly represented in the token list for each token type in the lexer.Contributor
Committer
In most cases, this should be a different person than the contributor.