Characters are not escaped when a code block's language is set to text

[AleksandrHovhannisyan]

Problem

When using fenced code blocks like this:

```text
some plain text code in here
```

The plain-text code is not properly escaped. So if it has < or >, those get rendered as literal tags and start throwing all kinds of HTML validation errors (this is currently affecting multiple pages on my site).

Steps to reproduce

1. Create a basic 11ty site with this plugin installed.
2. Create a markdown post with this code block:

```text
This <is> some text.
```

3. Observe that the rendered source has unescaped characters.

Example:

Question

Is this not how I should be using the text language? I can render fenced code blocks without specifying any language, but then I don't get any classes on the rendered pre/code or any nested spans. I was under the impression that text should still escape characters.

[zachleat]

text is a special escape hatch value in this plugin that opts out of syntax highlighting. If you want normal markdown escaping rules, remove text! See

eleventy-plugin-syntaxhighlight/src/markdownSyntaxHighlightOptions.js

Line 20 in 24f6212

if(language === "text") {

```
This <is> some text.
```

[zachleat]

As @svivian notes in #36 removing text also removes the styling but you can add a default class a la #66 (comment)