## Expected behavior Sometimes I want to write `@example` tags with code syntax inside. A contrived example: ````ts /** * @example * ``` * type Example = ElementType<string[]>; // string * ``` */ type ElementType<T> = T extends (infer Element)[] ? Element : never; ```` I should be allowed to use characters like `<` and `>`. ## Actual behavior `jsdoc/text-escaping` reports: ```plaintext You have unescaped HTML characters < or & in a tag ``` ...and autofixes the offending line to: ````ts * type Example = ElementType<string[]>; // string ```` ## ESLint Config ```js import jsdoc from 'eslint-plugin-jsdoc'; const config = [ // configuration included in plugin jsdoc.configs['flat/recommended'], // other configuration objects... { files: ['**/*.js'], plugins: { jsdoc, }, rules: { 'jsdoc/text-escaping': 'warn' } } ]; export default config; ``` ## ESLint sample See earlier. ```js // Format JS code here ``` <!-- OR, if this is not triggered by a single rule, what is the problem and how can one reproduce? --> ## Environment - Node version: <!-- $ node -v --> - ESLint version <!-- $ npx eslint -v --> - `eslint-plugin-jsdoc` version: