fix: fix space at end of table line

[UziTech]

Marked version: v3.0.2

Markdown flavor: GFM

Description

Fix ignore space after table line.

• Fixes Trailing whitespace at the end of table delimiter row breaks table rendering #2196

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/JCHBvjnQaXpBPM9gTPAUNRsX7dhN
✅ Preview: https://markedjs-git-fork-uzitech-table-space-markedjs.vercel.app

[calculuschild]

Edit: Bwahahahaha. Disregard. I misread the regex so this is all fine. Approved.

This solves the immediate problem, but I wanted to run a couple thoughts by you guys in case there is a deeper issue we should handle in following the (vague) GFM Spec:

1. Leading and trailing pipes | are not required on table rows. We currently don't allow for this on the delimiter row but perhaps we should for consistency with other cells, since I don't see anything in the Spec that says delimiter rows are exempted from this rule.
2. The spec says: "The delimiter row consists of cells whose only content are hyphens (-), and optionally, a leading or trailing colon (:), or both". However, it also says: "Spaces between pipes and cell content are trimmed." That is: trailing and leading spaces are not counted as part of the cell content. This indicates to me that a delimiter cell | :----: | should be a valid delimiter, since the cell's only content is :----: ; the spaces are trimmed and not considered part of the content. Edit: Looks like we already handle this one; I didn't realize.

If these are both true, then we might further adjust this PR to handle not just ending spaces, but also ending without a pipe at all.

So this would be a valid table:

a  |  b 
-- | -- 
c  |  d

And it works in Github:

a	b
c	d

But we currently can't handle it.

[github-actions]

🎉 This PR is included in version 3.0.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀