f6fac6c4bc
Fix bin/publish: use correct .env path for rspade_system Fix bin/publish script: prevent grep exit code 1 from terminating script 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
34 lines
1.2 KiB
JavaScript
Executable File
34 lines
1.2 KiB
JavaScript
Executable File
/// <reference lib="dom" />
|
|
|
|
/* eslint-env browser */
|
|
|
|
const element = document.createElement('i')
|
|
|
|
/**
|
|
* @param {string} value
|
|
* @returns {string|false}
|
|
*/
|
|
export function decodeNamedCharacterReference(value) {
|
|
const characterReference = '&' + value + ';'
|
|
element.innerHTML = characterReference
|
|
const char = element.textContent
|
|
|
|
// Some named character references do not require the closing semicolon
|
|
// (`¬`, for instance), which leads to situations where parsing the assumed
|
|
// named reference of `¬it;` will result in the string `¬it;`.
|
|
// When we encounter a trailing semicolon after parsing, and the character
|
|
// reference to decode was not a semicolon (`;`), we can assume that the
|
|
// matching was not complete.
|
|
// @ts-expect-error: TypeScript is wrong that `textContent` on elements can
|
|
// yield `null`.
|
|
if (char.charCodeAt(char.length - 1) === 59 /* `;` */ && value !== 'semi') {
|
|
return false
|
|
}
|
|
|
|
// If the decoded string is equal to the input, the character reference was
|
|
// not valid.
|
|
// @ts-expect-error: TypeScript is wrong that `textContent` on elements can
|
|
// yield `null`.
|
|
return char === characterReference ? false : char
|
|
}
|