Bug with Markdown Parser: Table Cell with Escaped Pipe

[Hosch250]

Describe the bug

Markdown parser--table cell generating \| for an escaped pipe instead of |.

Steps to Reproduce

Steps to reproduce the behavior:
This table:

| Input | Output |
|--|--|
|`{true \|\| true}`|`true`|
|`{true \|\| false}`|`true`|
|`{false \|\| true}`|`true`|
|`{false \|\| false}`|`false`|

Now correctly parses as 2 cells instead of 4, per my change for #2968. However, I forgot to make it remove the \ token from the parsed output, so the inline value contains \|\| instead of just ||.

Expected behavior

The \ character should not be displayed in the inline element.

Workaround:

This issue is easy to work around by replacing all \| with | when in a table cell context.

Environment

Package Version(s): 6.0.0

Windows 10 Build Number: Irrelevant
App min and target version: Irrelevant
Device form factor: Irrelevant
Visual Studio : All

Hello Hosch250, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will investigate the issue and help solve it ASAP. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

@Hosch250 This is a great catch and i am able to reproduce this as well. We can test out the PR once you have it ready.

[Hosch250]

Cool. It may take a little while as I'm running Linux on my personal computer ATM (needed to learn Docker), so I can't run the tests. I'll have to find a slow time at work or wait until I shift my personal computer back to Windows.

[Hosch250]

Status update: It only occurs within code blocks. If I remove the code ticks ``` from the table, it correctly escapes the pipe | in the text run. If I remove the ``, it still calculates the wrong number of cells. Is this a bug, or is it working as expected?

[Hosch250]

Since you guys are recommending everyone switch to MarkDig, should this issue be closed as won't-fix?

[Kyaa-dost]

@Hosch250 Thanks for checking. Will leave this open for now until we have more input in this from the community.