formatters examples appear as html-encoded text

See https://eslint.org/docs/latest/user-guide/formatters/

For example, the checkstyle example used to look like this:

But now it looks like this:

By checking deploy previews on PRs, it seems that this change was introduced by https://github.com/eslint/eslint/pull/16606

[chenxsan]

When using text language, we were actually opting-out of 11ty syntax highlighting. But I don’t think that’s the standard way to handle it.

Here’s how GitHub renders text language https://github.com/eslint/eslint/blob/main/docs/src/user-guide/formatters/index.md:

And this is how markdown-it renders it:

So I think it maybe more reasonable to decode the code block in the markdown source code instead of hacking on the new syntax highlighter with non-standard trick. Another benefit would be more readable code block.

[chenxsan]

Back to this formatters’ examples, I believe you’re right. We no longer need to escape them here formatter-examples.md.ejs. I’ve pushed a fix in #16669

Is this problem related to #16669? If not, it would be better to fix this in a separate PR.

More like an issue should be caught and fixed in https://github.com/eslint/eslint/pull/16606, though #16669 is a follow-up of https://github.com/eslint/eslint/pull/16606. I think it’s better to fix in a separate PR.