tftsr-devops_investigation/node_modules/decode-named-character-reference/index.dom.js

33 lines
1.0 KiB
JavaScript
Raw Normal View History

feat: initial implementation of TFTSR IT Triage & RCA application Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 03:36:25 +00:00
/// <reference lib="dom" />
/* global document */
const element = document.createElement('i')
/**
* @param {string} value
* @returns {string | false}
*/
export function decodeNamedCharacterReference(value) {
const characterReference = '&' + value + ';'
element.innerHTML = characterReference
const character = element.textContent
// Some named character references do not require the closing semicolon
// (`&not`, for instance), which leads to situations where parsing the assumed
// named reference of `&notit;` will result in the string `¬it;`.
// When we encounter a trailing semicolon after parsing, and the character
// reference to decode was not a semicolon (`&semi;`), we can assume that the
// matching was not complete.
if (
character.charCodeAt(character.length - 1) === 59 /* `;` */ &&
value !== 'semi'
) {
return false
}
// If the decoded string is equal to the input, the character reference was
// not valid.
return character === characterReference ? false : character
}