fix: fix items between lists

[UziTech]

Marked version: 2.0.0

Markdown flavor: Markdown.pl, CommonMark, GitHub Flavored Markdown

Description

• Check for end of list due to not enough indentation. fixes Whitespace after a list wraps all elements #1934
• Remove space token from list items. fixes Lexer: Space after list appears in last list_item #1947
• Fix > 3 spaces as continuation. CommonMark 282
• Fixes the following CommonMark tests: 225, 227, 246, 282, 283

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

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

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

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/6F33HfppZUivANHrhsUD9SbwzyDk
✅ Preview: https://markedjs-git-fork-uzitech-list-end-markedjs.vercel.app

[jackw]

Thanks so much for looking at this so quickly. I was wondering if there was any ETA on when this fix might make it into a release?

[UziTech]

@jackw it should be just a few days until this is released. Once we have two approvals from team members we can merge it.

[styfle]

👍

[calculuschild]

Looks good.

[calculuschild]

I'm ok to merge this, but this has become another area with lots of checks for the pedantic option threaded throughout. Is there a point when it would be more legible (and maybe faster) having all the pedantic logic together behind a single check, even if there is a bit of code reuse?

[UziTech]

Is there a point when it would be more legible (and maybe faster) having all the pedantic logic together behind a single check, even if there is a bit of code reuse?

Possibly not. I can't seem to find the conversation but I recall someone mentioning working on a whole different lexer and parser for pedantic and gfm. I don't know what ever happened to that.

I tend to prefer less code reuse so we don't have to remember to change the code in multiple places when updating it.

[github-actions]

🎉 This PR is included in version 2.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀