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>
27 lines
1.0 KiB
JavaScript
27 lines
1.0 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.hasMagic = void 0;
|
|
const minimatch_1 = require("minimatch");
|
|
/**
|
|
* Return true if the patterns provided contain any magic glob characters,
|
|
* given the options provided.
|
|
*
|
|
* Brace expansion is not considered "magic" unless the `magicalBraces` option
|
|
* is set, as brace expansion just turns one string into an array of strings.
|
|
* So a pattern like `'x{a,b}y'` would return `false`, because `'xay'` and
|
|
* `'xby'` both do not contain any magic glob characters, and it's treated the
|
|
* same as if you had called it on `['xay', 'xby']`. When `magicalBraces:true`
|
|
* is in the options, brace expansion _is_ treated as a pattern having magic.
|
|
*/
|
|
const hasMagic = (pattern, options = {}) => {
|
|
if (!Array.isArray(pattern)) {
|
|
pattern = [pattern];
|
|
}
|
|
for (const p of pattern) {
|
|
if (new minimatch_1.Minimatch(p, options).hasMagic())
|
|
return true;
|
|
}
|
|
return false;
|
|
};
|
|
exports.hasMagic = hasMagic;
|
|
//# sourceMappingURL=has-magic.js.map
|