Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

phillipb
Copy link
Contributor

@phillipb phillipb commented Dec 31, 2021

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

  • Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,

Committer

In most cases, this should be a different person than the contributor.

@vercel
Copy link

vercel bot commented Dec 31, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/markedjs/markedjs/8heK88jvf6Z7JZpS8ctiZnYCcij6
✅ Preview: https://markedjs-git-fork-phillipb-master-markedjs.vercel.app

Copy link
Member

@UziTech UziTech left a 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! 💯

@UziTech UziTech merged commit a9696e2 into markedjs:master Jan 6, 2022
github-actions bot pushed a commit that referenced this pull request Jan 6, 2022
## [4.0.9](v4.0.8...v4.0.9) (2022-01-06)

### Bug Fixes

* retain line breaks in tokens properly ([#2341](#2341)) ([a9696e2](a9696e2))
@github-actions
Copy link

github-actions bot commented Jan 6, 2022

🎉 This PR is included in version 4.0.9 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The lexer appears to handle new lines incorrectly
3 participants