Suppress false positive markdown violation

[adegeo]

Summary

This file is causing some linter errors on various PRs. This error is a false positive though and this PR disables that specific error check.

[Youssef1313]

The table doesn't render correctly (or at least in some parsers), so this isn't a false positive.

One possible fix is to use <code></code> instead of backticks, and use the encoding of the vertical bar. Not sure if there is a better solution.

[IEvangelist]

It does render correctly. See the live site:

[Youssef1313]

@IEvangelist Not by GitHub parser at least. I'm not sure whether you care about it being rendered correctly in both docs site and GitHub or only docs site. But I personally often view files in GitHub. So better if works in both.

[IEvangelist]

Hi @Youssef1313 Happy New Year!
I agree that it would be nice to have it render correctly in both, but my primary concern is the docs site. Instead of using <code></code>, are there any obvious or alternative approaches you have in mind that do not break the inline HTML concern/linting rules?

[Youssef1313]

@IEvangelist Happy new year to you too!

I'd probably ask @DavidAnson for help on this. I opened DavidAnson/markdownlint#363 asking for help on this.

Meanwhile, you can merge to fix the docs site, which is more important than GitHub-view.

[IEvangelist]

Looks good to me @adegeo, when you're ready.

[DavidAnson]

I fixed something that looks very much like this issue last month: #21977

Was that reverted for some reason?

[DavidAnson]

Doesn't seem reverted and still renders correctly on GitHub (and real site), it seems: https://github.com/dotnet/docs/blob/master/docs/standard/base-types/regular-expression-example-scanning-for-hrefs.md

Where isn't this working?

[Youssef1313]

@DavidAnson Thanks!

@adegeo It looks like you only need to merge master into your branch in the PR where markdownlint is failing

[adegeo]

For some reason my local fork wasn't pulling down the commit @DavidAnson added. I've cleaned and rebased and now I see it. odd. I think we can close this.