8839075805
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> |
||
|---|---|---|
| .. | ||
| xml | ||
| xmlns/1.0 | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| xmlchars.d.ts | ||
| xmlchars.js | ||
| xmlchars.js.map | ||
Utilities for determining whether characters belong to character classes defined by the XML specs.
Organization
It used to be that the library was contained in a single file and you could just
import/require/what-have-you the xmlchars module. However, that setup did not
work well for people who cared about code optimization. Importing xmlchars
meant importing all of the library and because of the way the code was
generated there was no way to shake the resulting code tree.
Different modules cover different standards. At the time this documentation was last updated, we had:
xmlchars/xml/1.0/ed5which covers XML 1.0 edition 5.xmlchars/xml/1.0/ed4which covers XML 1.0 edition 4.xmlchars/xml/1.1/ed2which covers XML 1.0 edition 2.xmlchars/xmlns/1.0/ed3which covers XML Namespaces 1.0 edition 3.
Features
The "things" each module contains can be categorized as follows:
-
"Fragments": these are parts and pieces of regular expressions that correspond to the productions defined in the standard that the module covers. You'd use these to build regular expressions.
-
Regular expressions that correspond to the productions defined in the standard that the module covers.
-
Lists: these are arrays of characters that correspond to the productions.
-
Functions that test code points to verify whether they fit a production.