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> |
||
|---|---|---|
| .. | ||
| index.d.ts | ||
| index.js | ||
| license | ||
| package.json | ||
| readme.md | ||
character-entities-legacy
List of legacy HTML named character references that don’t need a trailing semicolon.
Contents
- What is this?
- When should I use this?
- Install
- Use
- API
- Types
- Compatibility
- Security
- Related
- Contribute
- License
What is this?
This is a list of certain named character references, that due to legacy
reasons, don’t need a trailing semicolon in HTML.
For example, © is perfectly fine for ©!
When should I use this?
Maybe when you’re writing an HTML parser or minifier, but otherwise probably
never!
Even then, it might be better to use parse-entities or
stringify-entities.
Install
This package is ESM only. In Node.js (version 12.20+, 14.14+, or 16.0+), install with npm:
npm install character-entities-legacy
In Deno with Skypack:
import {characterEntitiesLegacy} from 'https://cdn.skypack.dev/character-entities-legacy@2?dts'
In browsers with Skypack:
<script type="module">
import {characterEntitiesLegacy} from 'https://cdn.skypack.dev/character-entities-legacy@2?min'
</script>
Use
import {characterEntitiesLegacy} from 'character-entities-legacy'
console.log(characterEntitiesLegacy.includes('copy')) // => true
console.log(characterEntitiesLegacy.includes('frac34')) // => true
console.log(characterEntitiesLegacy.includes('sup1')) // => true
API
This package exports the following identifiers: characterEntitiesLegacy.
There is no default export.
characterEntitiesLegacy
List of (case sensitive) legacy character entity names.
wooorm/character-entities holds their decoded values.
See whatwg/html for more info.
Types
This package is fully typed with TypeScript.
Compatibility
This package is at least compatible with all maintained versions of Node.js. As of now, that is Node.js 12.20+, 14.14+, and 16.0+. It also works in Deno and modern browsers.
Security
This package is safe.
Related
wooorm/parse-entities— parse (decode) character referenceswooorm/stringify-entities— serialize (encode) character referenceswooorm/character-entities— info on character entitieswooorm/character-entities-html4— info on HTML4 character entitieswooorm/character-reference-invalid— info on invalid numeric character references
Contribute
Yes please! See How to Contribute to Open Source.