Paragraph text is split into separate tokens when using backslash

[calculuschild]

Marked version: 1.2.7

Describe the bug
The inline.text rules seem to be splitting inline text when it encounters a backslash, resulting in two separate text tokens inside a paragraph token.

To Reproduce
Observe on the demo.

First second results in:

[
{type:"paragraph", raw:"First second", text:"First second", tokens:[
  {type:"text", raw:"First second", text:"First second"}
]}
]

But First\second results in

[
{type:"paragraph", raw:"First\\second", text:"First\\second", tokens:[
  {type:"text", raw:"First", text:"First"}
  {type:"text", raw:"\\second", text:"\\second"}
]}
]

Expected behavior
While the resulting HTML is the same, this causes issues when using, for instance, a custom text renderer. The expected string is instead sliced into multiple parts, which prevents handling of the complete string as a whole.

Either the two consecutive text tokens should be joined as they are in the "block" text, or the inline.text rules need to be fixed to not stop at the first backslash.

[UziTech]

Hmm ... It looks like the block text combines the text tokens I think we could do something similar to inline text tokens.

[github-actions]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀